Hacker News new | ask | show | jobs
by pilif 4249 days ago
I would agree, but the fact that it suddenly stopped working points to carrier interference rather than Heroku (because as a developer focussed company, they would have informed OPs company of the change)
3 comments

It seems it is on Heroku's end. https://news.ycombinator.com/item?id=8515164
Heroku isn't in a frozen state. I'm sure that they change the code daily. The fact that it suddently stopped working doesn't really point to any specific endpoint unless you know which ones have changed. Then it might mean something.
Or perhaps they would have noticed increased error rates for a client and investigated. Monitoring right?