DatoCMS Status: Incident History
to 
Requests slow/failing
Normal behaviour is fully restored, resolving the ticket.
Problems when reading / saving some kind of records through our admin interface
The issue is resolved
Connectivity issues
Heroku posted a post-mortem update: https://status.heroku.com/incidents/2359
Vercel build notifications not working
We've talked with Vercel, and they've told us that the only way to make notifications work again is by redoing the integration process. To do that, enter the failing Build Trigger in DatoCMS and press the "Authorize Vercel" button again.
High number of failing requests
Everything is back to normal
Slow responses on CMA
Everything is OK now. We'll update this later if one of our hosting partners writes down something on their status pages.