Is Agora (legacy — broken-pubDate generic_rss; replaced by id 6370) down?

Last checked 5m ago
Current status
Agora (legacy — broken-pubDate generic_rss; replaced by id 6370) has degraded performance

7 active incidents: 【China】Real-Time Communication Some call sessions have expe…, 【Southeast Asia】Interactive Whiteboard Some API requests in… · +5 more

Official status page: https://status.agora.io · Polled every 5 minutes · 0 components tracked

Real-time Agora (legacy — broken-pubDate generic_rss; replaced by id 6370) status, recent outages, and incident history — pulled directly from Agora (legacy — broken-pubDate generic_rss; replaced by id 6370)'s official status page at https://status.agora.io every 5 minutes. Pingoru tracks 0 Agora (legacy — broken-pubDate generic_rss; replaced by id 6370) services and has captured 10 incidents in the last 90 days (97.78% uptime). Get email, Slack, Discord, or webhook alerts the moment Agora (legacy — broken-pubDate generic_rss; replaced by id 6370) reports a new incident — free for 5 monitors, no credit card.

Agora (legacy — broken-pubDate generic_rss; replaced by id 6370) uptime 97.78% uptime · past 90 days
Mon Wed Fri
JanFebMarApr
Less More

Recent outages & incidents

Past 7 days
  1. Ongoing ● 11h 55m
    Started Apr 29, 2026, 05:26 AM UTC
    1 update · show timeline
    • monitoring · Apr 21, 2026, 10:36 PM UTC

      <p> <small>Posted Dec 29, 2024 - 04:32 AM UTC</small><br /> <strong>Investigating</strong><br /> We have observed that Some call sessions have experience degrade in certain areas in China for Real-Time Communication in China, and we are currently investigating. </p> <p> <small>Posted Dec 29, 2024 - 04:36 AM UTC</small><br /> <strong>Identified</strong><br /> We have identified the cause of the issue and are currently working on a fix. </p> <p> <small>Posted Dec 29, 2024 - 06:30 AM UTC</small><br /> <strong>Update</strong><br /> We are continuing to work on a fix for this issue. </p> <p> <small>Posted Dec 29, 2024 - 08:37 AM UTC</small><br /> <strong>Update</strong><br /> The fix has been implemented, and we are monitoring to see if it effectively resolves the issue. </p> <p> <small>Posted Dec 29, 2024 - 10:30 AM UTC</small><br /> <strong>Resolved</strong><br /> The issue has been resolved, and we are continuously monitoring the online status. </p> <p> <small>Posted Dec 31, 2024 - 07:59 AM UTC</small><br /> <strong>Summarize</strong><br /> During the period from December 29, 2024, 04:20 (UTC) to December 29, 2024, 10:00 (UTC), we discovered some abnormal traffic in certain data centers of the Real-Time Communication service. A small number of users may have experienced a degrade in service quality. After taking targeted measures to address the abnormal traffic, the service has been restored. </p>

    Latest: <p> <small>Posted Dec 29, 2024 - 04:32 AM UTC</small><br /> <strong>Investigating</strong><br /> We have observed that Some call sessions have experience degrade in certain areas i…

  2. Ongoing ● 11h 55m
    Started Apr 29, 2026, 05:26 AM UTC
    1 update · show timeline
    • monitoring · Apr 21, 2026, 10:36 PM UTC

      <p> <small>Posted Jan 7, 2025 - 09:47 AM UTC</small><br /> <strong>Summarize</strong><br /> During the period from 2025-01-02 04:11:00 (UTC) to 2025-01-03 06:35:00 (UTC), an abnormal status of a routing node for the interactive whiteboard service caused some API access failures. After removing the faulty node, the issue was resolved. </p>

    Latest: <p> <small>Posted Jan 7, 2025 - 09:47 AM UTC</small><br /> <strong>Summarize</strong><br /> During the period from 2025-01-02 04:11:00 (UTC) to 2025-01-03 06:35:00 (UTC), an abnorm…

  3. Ongoing ● 11h 55m
    Started Apr 29, 2026, 05:26 AM UTC
    1 update · show timeline
    • monitoring · Apr 21, 2026, 10:36 PM UTC

      <p> <small>Posted Mar 25, 2025 - 10:57 AM UTC</small><br /> <strong>Summarize</strong><br /> Between 2025-03-23 22:37 UTC and 2025-03-24 19:53 UTC, the Agora Chat Service North American data center experienced multiple short-term performance decline due to abnormal traffic spikes. We implemented necessary measures to address the abnormal traffic. Currently, the data center has resumed normal service status. </p>

    Latest: <p> <small>Posted Mar 25, 2025 - 10:57 AM UTC</small><br /> <strong>Summarize</strong><br /> Between 2025-03-23 22:37 UTC and 2025-03-24 19:53 UTC, the Agora Chat Service North Ame…

  4. Ongoing ● 11h 55m
    Started Apr 29, 2026, 05:26 AM UTC
    1 update · show timeline
    • monitoring · Apr 21, 2026, 10:36 PM UTC

      <p> <small>Posted Apr 18, 2025 - 01:15 PM UTC</small><br /> <strong>Summarize</strong><br /> Between 2025-04-18 10:40 (UTC) and 2025-04-18 11:00 (UTC), the Interactive Whiteboard service in the China region experienced a degradation in service quality due to a sudden surge in traffic. After implementing emergency capacity expansion, the service returned to normal operation. </p>

    Latest: <p> <small>Posted Apr 18, 2025 - 01:15 PM UTC</small><br /> <strong>Summarize</strong><br /> Between 2025-04-18 10:40 (UTC) and 2025-04-18 11:00 (UTC), the Interactive Whiteboard s…

  5. Ongoing ● 11h 55m
    Started Apr 29, 2026, 05:26 AM UTC
    1 update · show timeline
    • monitoring · Apr 21, 2026, 10:36 PM UTC

      <p> <small>Posted May 14, 2025 - 03:18 AM UTC</small><br /> <strong>Summarize</strong><br /> From 2025-05-14 02:06 (UTC) to 2025-05-14 02:25 (UTC), due to an anomaly in the login success rate data statistics service, the 'SD-RTN™ Join Experience Indicator' metric experienced fluctuations. There was no actual impact on customer experience. The statistical anomaly issue has now recovered. </p>

    Latest: <p> <small>Posted May 14, 2025 - 03:18 AM UTC</small><br /> <strong>Summarize</strong><br /> From 2025-05-14 02:06 (UTC) to 2025-05-14 02:25 (UTC), due to an anomaly in the login s…

See the full Agora (legacy — broken-pubDate generic_rss; replaced by id 6370) outage history

5 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.

Sign up free to unlock full history

10 free monitors · No credit card

Outage history

Past 30 days · 10 incidents
  • 【China】Real-Time Communication Some call sessions have experience degrade in certain areas in China Ongoing
    Started Apr 29, 2026, 05:26 AM UTC · ● 11h 55m
  • 【Southeast Asia】Interactive Whiteboard Some API requests in the Southeast Asia region have failed Ongoing
    Started Apr 29, 2026, 05:26 AM UTC · ● 11h 55m
  • 【North America】Agora Chat Agora Chat Service North American cluster experienced multiple short-term performance decline Ongoing
    Started Apr 29, 2026, 05:26 AM UTC · ● 11h 55m
  • 【China】Interactive Whiteboard performance degradation in the China region service cluster Ongoing
    Started Apr 29, 2026, 05:26 AM UTC · ● 11h 55m
  • 【Global】Real-Time Communication Login success rate data statistics anomaly leads to abnormal fluctuations in the 'SD-RTN™ Join Experience Indicator' metric Ongoing
    Started Apr 29, 2026, 05:26 AM UTC · ● 11h 55m
  • 【Global】Real-Time Communication Abnormal statistics of login success rate data affect the display of the 'SD-RTN™ Join Experience Indicator' status, with no actual impact on customer experience Resolved
    Started Apr 29, 2026, 05:26 AM UTC · Resolved Apr 29, 2026, 05:26 AM UTC ·
  • 【Global】Cloud Recording The data statistical anomaly has caused an incorrect display of the cloud recording service status, with no actual impact on customer experience Ongoing
    Started Apr 29, 2026, 05:26 AM UTC · ● 11h 55m
  • 【China,Southeast Asia】Real-Time Communication The login delay for some users has increased Resolved
    Started Apr 29, 2026, 05:26 AM UTC · Resolved Apr 29, 2026, 05:26 AM UTC ·

See Agora (legacy — broken-pubDate generic_rss; replaced by id 6370) in your Pingoru dashboard

Monitor Agora (legacy — broken-pubDate generic_rss; replaced by id 6370) alongside every other service your stack depends on — same alerts, same timeline, same calendar — all in one place.

Every status page, one dashboard

Add Agora (legacy — broken-pubDate generic_rss; replaced by id 6370) to your Pingoru monitors and it sits next to AWS, Stripe, GitHub, and every other vendor in your stack — a single dashboard for the live status of every cloud and SaaS provider you depend on. One subscription, one inbox, every incident.

Incident timeline, this provider or all of them

Every Agora (legacy — broken-pubDate generic_rss; replaced by id 6370) incident — when it started, when it resolved, which services were affected, how bad it was, how long it lasted — laid out in one feed you can scan in 30 seconds. Filter to just Agora (legacy — broken-pubDate generic_rss; replaced by id 6370) or see every provider at once.

Maintenance calendar

Scheduled Agora (legacy — broken-pubDate generic_rss; replaced by id 6370) maintenance windows land in the same calendar as every other vendor you depend on — see what's running now, what's coming up, and a calendar view. Plan around your vendors instead of being caught out by them.

Every Agora (legacy — broken-pubDate generic_rss; replaced by id 6370) status change, one inbox

Pingoru watches Agora (legacy — broken-pubDate generic_rss; replaced by id 6370)'s official status page every 5 minutes and delivers incident, resolution, and maintenance events to your email, Slack, Discord, Teams, or webhook.

Only alert on the services you use

Subscribe to the specific Agora (legacy — broken-pubDate generic_rss; replaced by id 6370) services you rely on. Everything else stays silent.

Email + Slack + Discord + Teams

Signed webhooks on every plan. Route Agora (legacy — broken-pubDate generic_rss; replaced by id 6370) alerts wherever your team already lives — no per-integration billing, no tier-gating the channels that matter.

Maintenance, not surprises

Upcoming Agora (legacy — broken-pubDate generic_rss; replaced by id 6370) maintenance windows appear in your maintenance calendar days in advance. Plan deploys and rollouts around them instead of finding out during an incident.

Fine-grained alert control

Per-monitor switches for opened, updated, resolved, and maintenance events. Silence the noisy Agora (legacy — broken-pubDate generic_rss; replaced by id 6370) services without silencing the monitor entirely.

Invite your team

Premium includes 10 team seats. Everyone watching Agora (legacy — broken-pubDate generic_rss; replaced by id 6370) from the same account, with per-user notification preferences for any monitor.

Get notified on Agora (legacy — broken-pubDate generic_rss; replaced by id 6370) status changes

Pingoru watches Agora (legacy — broken-pubDate generic_rss; replaced by id 6370)'s official status page and sends your team instant alerts when incidents open, change severity, or resolve. Route notifications to email, Slack, Discord, or a webhook — wherever your team already lives.

Start monitoring Agora (legacy — broken-pubDate generic_rss; replaced by id 6370) free

Monitor Agora (legacy — broken-pubDate generic_rss; replaced by id 6370) along with everything else

Pingoru tracks 6,000+ cloud and SaaS status pages in one dashboard. Add Agora (legacy — broken-pubDate generic_rss; replaced by id 6370) and every other provider you depend on — AWS, Stripe, GitHub, Cloudflare, OpenAI — and get a single view of the health of every service your app depends on.

Browse the full service directory

Track Agora (legacy — broken-pubDate generic_rss; replaced by id 6370) uptime & incident history

See 90 days of Agora (legacy — broken-pubDate generic_rss; replaced by id 6370) uptime at a glance, with every past incident linked to its component and update timeline. Export the history as CSV or JSON for SLA reports, postmortems, or vendor evaluations — data your team actually needs, not marketing numbers.

See Agora (legacy — broken-pubDate generic_rss; replaced by id 6370) uptime history

Frequently asked questions

What is Agora (legacy — broken-pubDate generic_rss; replaced by id 6370)'s uptime?
Over the last 90 days, Agora (legacy — broken-pubDate generic_rss; replaced by id 6370) reported 97.78% uptime on its official status page. That figure is calculated from the public incident timeline at https://status.agora.io — each minute of degraded, partial-outage, or major-outage status counts against the total. Sign up to Pingoru free to see Agora (legacy — broken-pubDate generic_rss; replaced by id 6370)'s uptime history rolling forward in real time.
Has Agora (legacy — broken-pubDate generic_rss; replaced by id 6370) had outages in 2026?
Yes — Agora (legacy — broken-pubDate generic_rss; replaced by id 6370) has had 3 incidents reported on its official status page so far in 2026. The full timeline (start times, durations, components affected) is shown above on this page. Pingoru re-checks the status page every 5 minutes so the count stays current.
When was the last Agora (legacy — broken-pubDate generic_rss; replaced by id 6370) outage?
The most recent Agora (legacy — broken-pubDate generic_rss; replaced by id 6370) incident was "【Global】Real-Time Communication Abnormal statistics of login success rate data affect the display of the 'SD-RTN™ Join Experience Indicator' status, with no actual impact on customer experience", which started on April 29, 2026 and was resolved on April 29, 2026. Pingoru captured this directly from https://status.agora.io. See the full incident card above for affected components and the update timeline.
How often does Agora (legacy — broken-pubDate generic_rss; replaced by id 6370) have outages?
Based on the last 90 days, Agora (legacy — broken-pubDate generic_rss; replaced by id 6370) averages 1.0 reported incident per month on its official status page. Pingoru tracks each one with start time, duration, severity, and affected components — so you can see the pattern at a glance instead of digging through the vendor's archive.
Where is Agora (legacy — broken-pubDate generic_rss; replaced by id 6370)'s status page?
Agora (legacy — broken-pubDate generic_rss; replaced by id 6370)'s official status page is https://status.agora.io. Pingoru polls it every 5 minutes and renders the same data here, alongside every other cloud or SaaS provider you depend on — so you can spot multi-vendor incidents (e.g. AWS + Stripe + Cloudflare degrading at the same minute) without flipping between tabs.
Is Agora (legacy — broken-pubDate generic_rss; replaced by id 6370) down right now?
Agora (legacy — broken-pubDate generic_rss; replaced by id 6370) has degraded performance. Pingoru checks the official status page every 5 minutes and flips this headline the moment Agora (legacy — broken-pubDate generic_rss; replaced by id 6370) reports a change. Current status is based on 0 tracked services.
How does Pingoru know if Agora (legacy — broken-pubDate generic_rss; replaced by id 6370) is down?
We read https://status.agora.io directly, using Agora (legacy — broken-pubDate generic_rss; replaced by id 6370)'s own status page. If the vendor reports an incident, you see it within one check cycle — not after someone manually marks the page as down.
Where can I get notified when Agora (legacy — broken-pubDate generic_rss; replaced by id 6370) has an outage?
Create a free Pingoru account and add Agora (legacy — broken-pubDate generic_rss; replaced by id 6370) as a monitor. You can filter to specific services, pick severity thresholds, and route alerts via email, Slack, Discord, or a webhook.
Agora (legacy — broken-pubDate generic_rss; replaced by id 6370)'s status page says the service is up, but I'm having issues — what's wrong?
Three common reasons: • A real Agora (legacy — broken-pubDate generic_rss; replaced by id 6370) incident that hasn't been acknowledged on their public status page yet — vendor status pages are updated manually and typically lag the first customer reports by 10–30 minutes. • A regional or account-scoped issue affecting a subset of customers — these rarely trigger a global status-page change. • A local problem: ISP / DNS / your own software. Try reproducing from a mobile data connection and from a different network to isolate. If you suspect a real Agora (legacy — broken-pubDate generic_rss; replaced by id 6370) issue that isn't reflected yet, contact their support to escalate. Subscribing here means you get the alert the moment they do post an update.
Where does Pingoru get the official Agora (legacy — broken-pubDate generic_rss; replaced by id 6370) status?
We use Agora (legacy — broken-pubDate generic_rss; replaced by id 6370)'s own status page at https://status.agora.io and cross-reference their homepage (https://www.agora.io/en). Nothing is read in a way the vendor hasn't explicitly made public — we use the same data their own dashboard uses. So our data is as accurate as what you'd see loading the status page yourself, but rolled into one dashboard alongside every other service you depend on.
What does "Degraded" mean?
Agora (legacy — broken-pubDate generic_rss; replaced by id 6370) is reporting degraded performance — services are up but slower than usual, or a subset of requests is failing.

Stop finding out from your users.

We watch Agora (legacy — broken-pubDate generic_rss; replaced by id 6370)'s official status page every 5 minutes. The moment they report an incident, you get an email — often before the outage is widely noticed.

Monitor Agora (legacy — broken-pubDate generic_rss; replaced by id 6370) free →

10 monitors free · email alerts · no credit card

Want the full picture first? See everything Pingoru does →