4 ms·

Backblaze down again due to DNS issues

• ratsmack 6y ago
  It makes me wonder if they will learn their lesson this time around.
  • stevenhubertron 6y ago
    What lesson is that? Seriously I don't know.
    • jsiepkes 6y ago
      Don't host your DNS at GoDaddy. If Backblaze's entire DNS gets suspended if just one of their customers hosts offending content that's just unacceptable.
    • ratsmack 6y ago
      They need to improve the reliability the their DNS by partnering with a provider that won't back stab them.
    • frombody 6y ago
      Don't build your enterprise on consumer grade services.
• lpellis 6y ago
  They really should get a public status page, only way to know if problem is their side is twitter. Then again, companies rarely update the status to down..
• mattjaynes 6y ago
  "UPDATE: we are coming back online slowly (as it’s a DNS issue it may take a while to propagate). We apologize for the disruption and are working to make sure it does not happen again." https://twitter.com/backblaze/status/1362139948694966272 https://twitter.com/backblaze/status/1362139948694966272 Insane that this exact thing happened a few days ago and they still haven't switched from Godaddy. Hope this really inspires them to take their customers seriously. This was really painful. Service disrupted for many thousands of customers.
  • ratsmack 6y ago
    At a minimum, they should regularly publish their static IP address via Twitter and/or email until they are certain the reliability of domain name provider has returned. Edit: They did publish their IP's this time. https://twitter.com/backblaze/status/1362132502467407875 https://twitter.com/backblaze/status/1362132502467407875