Rare Dos Infection (latest batch)

Discussion in 'Trade Talk' started by Treebs, Aug 3, 2013.

Thread Status:
Not open for further replies.
  1. brownswisscow

    brownswisscow Crusader (476) Feb 9, 2012 Vermont

    Also had 2 drain pours :slight_frown:
     
  2. cavedave

    cavedave Grand Pooh-Bah (4,157) Mar 12, 2009 New York
    In Memoriam Pooh-Bah Trader

    It didn't used to be bad manners to reply in the offer thread that some are reported infected.
     
  3. franklinn

    franklinn Initiate (0) May 29, 2012 Vermont

    So far no one has had issues with the rareR. They havnt said explicitly yet, but there's been mention of replacing growlers of rare with another brew.
     
  4. striker2160

    striker2160 Savant (1,172) May 5, 2013 Minnesota
    Trader

    We have one coming up from Florida on a trade. We are crossing our fingers.
     
  5. joetouchton

    joetouchton Initiate (0) Apr 23, 2012 Delaware

    i got one as an extra hope its not infected also
     
  6. Treebs

    Treebs Pooh-Bah (1,728) Apr 18, 2011 Illinois
    Pooh-Bah Trader

    I've exchanged a few emails with Doug. Couldn't have been more appreciative of the feedback and also classy in the way they are handling this. Stand-up guy and operation they got at Peg's/Cycle Brewing.
     
  7. cavedave

    cavedave Grand Pooh-Bah (4,157) Mar 12, 2009 New York
    In Memoriam Pooh-Bah Trader

    No dogs in this fight, but how are they handling this for you?
     
  8. Treebs

    Treebs Pooh-Bah (1,728) Apr 18, 2011 Illinois
    Pooh-Bah Trader


    They are going to reimburse my trade partner (either refund or new beer). Since they can't legally ship beer to me they are putting together a "sorry" package. Basically taking care of all parties involved from what I understand.
     
    cfh64, MarkIntihar and cavedave like this.
  9. iadler

    iadler Initiate (0) Aug 12, 2009 Illinois

    I got 4 growlers...hoping for the best, though it's nice to hear they are handling the situation as best they can.
     
  10. nanobrew

    nanobrew Initiate (0) Dec 31, 2008 California

    I have only had the RARER DOS and it was infected. The person who sent it says that when they opened theirs the majority were infected too.
     
  11. cacostaj

    cacostaj Zealot (579) Feb 15, 2013 Florida

    Technically, if an infection is random from growler to growler, how can someone "withhold" any info? I picked up 6 rare, 5 nooners and 2 rareR directly from Pegs. Have either drank and or traded all but 1 rare and haven't had one infected growler.
     
  12. whiskey

    whiskey Maven (1,308) Feb 25, 2012 California
    Trader

    Not sure if serious.jpeg
     
  13. cbeer88

    cbeer88 Initiate (0) Sep 5, 2007 Massachusetts


    If you know a beer has a reasonable chance of being infected, it's poor form to put it up in ISO:FT without at least mentioning that fact. You may have not experienced it, and it's highly possible you may not have known there is an issue when you traded them, but now you do know.

    Some unscrupulous people will absolutely try to pawn off beers with infection issues on unsuspecting traders.
     
    OtisCampbell, Clonies720 and Deltoro like this.
  14. iadler

    iadler Initiate (0) Aug 12, 2009 Illinois

    Just cracked open 2 growlers and both were infected. At first, the infection was barely noticeable but after a few minutes, tart cherries became completely dominant. Hope one of my last two from a different trader differ, but am expecting the same results. What a shame.
     
  15. CaptainFleeker

    CaptainFleeker Initiate (0) Aug 27, 2012 Illinois
    Trader

    I wish you were wrong but you are right. I have seen some Rare DOS growlers up for trade in the FT:ISO forum in the past few days with no disclosures. Some from people who regulary comment in the South Atlantic forum. I found out about potential issues last Thursday/Friday and spent the next couple of days contacting all my trading partners that I sent one to notifying them there *could* be a problem. Hopefully others are doing the same. Some reported back all was well, others had problems but didnt know there was a program put in place. The reason notifying your trading partners is so important is that Peg's/Cycle Brewing has established a cutoff date of August 21st to notify them of bad growlers. Some people are under the misconception that these growlers can be aged for more than a month when they really can't/shouldn't. If they sit on these and miss the cutoff they run the risk of Peg's/Cycle Brewing not doing anything for them.

    Here is some more info directly from Peg's:

    http://beeradvocate.com/community/threads/rare-dos.103382/page-3#post-1576313
     
    JulianB, kpanter and Deltoro like this.
  16. wiltznucs

    wiltznucs Initiate (0) Jun 27, 2013 Florida

    Raises hand, had a bad RareR here. All purchased direct from Peg's and stored in a proper environment. Opened two RareR's this past week and the difference between the good and bad was night and day. 4 out of 6 Rares ended up bad for me, 1 out of two RareR's I've opened and I'm gonna be dipping into Nooner this week.
     
  17. nanobrew

    nanobrew Initiate (0) Dec 31, 2008 California


    I have had an issue with RareR
     
  18. pmoney

    pmoney Initiate (0) Apr 15, 2011 Illinois

    From this most recent batch? What was the issue?
     
  19. nanobrew

    nanobrew Initiate (0) Dec 31, 2008 California


    when was the most recent one. I stopped paying attention to the release after my heart break of that infected bottle. It was one of my most anticipated beers, as I love rum, and had never tried this or the base beer. I drank mine in March, and I know it had at least a month of age on it. I know they say drink fresh, I drank it as soon as I received it, but I have saved growler fills of beers for much longer with no issue. Also, the person who sent it to me (as a gift, not a trade), said they had a high percentage of similar results, even when fresh, he was hoping mine would be a good one.
     
  20. pmoney

    pmoney Initiate (0) Apr 15, 2011 Illinois

    Oh yeah, that's not this most recent batch. You had me concerned there for a second!
     
Thread Status:
Not open for further replies.