Minor · almost 2 years ago · lasted 3 months
We are investigating the root cause.
Minor · almost 2 years ago · lasted 4 months
We are seeing increased errors from Twilio's API as well as increased connection latency. This is preventing our Linguists and Agents from transferring as well as performing other actions while on calls. We have reached out to our Twilio team and are awaiting more information.
Minor · almost 5 years ago · lasted over 3 years
We are currently experiencing issues advancing calls through our telephony platforms workflow to consistently reach our agents and interpreters. We are actively working on resolving this issue with our telephony team. At this time some of our inbound calls are not reaching their intended recipient. Next update in 30 minutes.
Minor · over 5 years ago · lasted about 4 years
Our telephony provider is currently experiencing a massive issue with outbound calls that is preventing us from connecting inbound callers to resources. They are currently investigating the issue.
Minor · almost 6 years ago · lasted over 4 years
We are experiencing an issue with performance in our Database which is causing general performance issues in GLOBO HQ. We are working with our database provider to resolve as quickly as possible.
Minor · about 6 years ago · lasted over 4 years
A database migration is taking longer than expected and is causing some users to get errors while access GLOBO HQ. This should be resolved shortly once the migration completed.
Get notified only when an outage impacts a certain component.
SaaS rules the world, and all teams depend on them to do their most productive work. IsDown helps you monitor all your cloud services, so you can focus on what matters.
Try it out! How much time you'll save your team, by having the outages information close to them?