All Systems Operational
Uptime over the past 90 days. View historical uptime.
Meeting API Operational
90 days ago
100.0 % uptime
Today
Create Meeting Operational
90 days ago
100.0 % uptime
Today
Add Participant Operational
90 days ago
100.0 % uptime
Today
Get User Preset Operational
90 days ago
100.0 % uptime
Today
Recordings ? Operational
90 days ago
100.0 % uptime
Today
Meeting V2 API Operational
90 days ago
100.0 % uptime
Today
Create Meeting Operational
90 days ago
100.0 % uptime
Today
Delete Participant Operational
90 days ago
100.0 % uptime
Today
Delete Preset Operational
90 days ago
100.0 % uptime
Today
Create Preset Operational
90 days ago
100.0 % uptime
Today
Add Participant Operational
90 days ago
100.0 % uptime
Today
Media Operational
90 days ago
100.0 % uptime
Today
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.

No incidents or maintenance related to this downtime.

System Metrics Month Week Day
API Response Time
Fetching
Error Rate
Fetching
Past Incidents
Jul 27, 2024

No incidents reported today.

Jul 26, 2024

No incidents reported.

Jul 25, 2024

No incidents reported.

Jul 24, 2024

No incidents reported.

Jul 23, 2024

No incidents reported.

Jul 22, 2024

No incidents reported.

Jul 21, 2024

No incidents reported.

Jul 20, 2024
Service Interruption: Video Calls unavailable for a subset of customers
Resolved - Date and Time: 20th July 00:35 IST to 20th July 01:30 IST (19 July 19:05 to 19 July 20:00 UTC)

Affected Service: Video Calls

Issue: Video calls on the new media layer were unavailable for a period of about 55 minutes.

Root Cause: During a routine maintenance task, permissions associated with a class of instances were accidentally revoked. As a result, a service that manages the state of calls on the new media engine was unavailable, causing this interruption.

Resolution: Our engineering team has identified and fixed the issue by fixing the permissions with the instances. The maintenance task has been paused, and will be resumed after reviewing the health of all associated systems.

Impact: Existing calls abruptly ended, and new calls would not have started due to this interruption. This only affected organisations using the new media layer. The older media layer continued functioning, and some calls would have been rerouted to the working systems.

Next Steps:

* Provide a detailed RCA on Monday
* Fix the underlying infrastructure code to prevent this revocation of permissions from happening again
* Complete the maintenance task
Jul 20, 00:30 IST
Jul 19, 2024
Service Interruption: Meetings API returning 500
Resolved - Date and Time: Friday (19th July 2024) 4:15 AM to 4:30 AM IST (11 PM Thursday 18th July UTC)

Duration: 15 mins

Issue: /v2/meetings API was returning 500 response

Root Cause: It was investigated that one of our read routes experienced a huge request spike and caused our read DB to choke. Since this was not our service critical route, status alerts did not go up. However, secondary alerts were in place, which alerted the team. However, the spike had died down, and the system had recovered before taking any measures.

Resolution: System auto recovered

Next Steps:

Our team is designing rate limits on non-critical critical paths to avoid such errors in the future.
Jul 19, 04:15 IST
Jul 18, 2024

No incidents reported.

Jul 17, 2024

No incidents reported.

Jul 16, 2024

No incidents reported.

Jul 15, 2024

No incidents reported.

Jul 14, 2024

No incidents reported.

Jul 13, 2024

No incidents reported.

← Incident History Powered by Atlassian Statuspage