privy - Notice history

All systems operational

APIs - Operational

100% - uptime
Apr 2025 · 100.0%May · 100.0%Jun · 100.0%

Previous page

Next page

Apr 2025
May 2025
Jun 2025

Webhooks - Operational

100% - uptime
Apr 2025 · 100.0%May · 100.0%Jun · 100.0%

Previous page

Next page

Apr 2025
May 2025
Jun 2025

SDKs - Operational

100% - uptime
Apr 2025 · 100.0%May · 100.0%Jun · 100.0%

Previous page

Next page

Apr 2025
May 2025
Jun 2025

Dashboard - Operational

100% - uptime
Apr 2025 · 100.0%May · 100.0%Jun · 100.0%

Previous page

Next page

Apr 2025
May 2025
Jun 2025

Wallet Connectors - Operational

100% - uptime
Apr 2025 · 100.0%May · 100.0%Jun · 100.0%

Previous page

Next page

Apr 2025
May 2025
Jun 2025

Third Party: Amazon Web Services – AWS → AWS health - Operational

Notice history

Jun 2025

X (fka Twitter) API experiencing outage
  • Resolved
    Resolved

    This incident has been resolved according to reports about X (fka Twitter).

  • Identified
    Identified

    We are monitoring the API status at: https://statusgator.com/services/twitter-api.

  • Investigating
    Investigating

    The X (fka Twitter) API is experiencing issues.

Elevated latency
  • Resolved
    Resolved
    This incident has been resolved.
  • Monitoring
    Monitoring
    We are continuously monitoring the situation.
  • Investigating
    Investigating

    APIs are all fully functional but seeing elevated latency. We are continuing to work on a fix for this incident.

Embedded wallet partial outage
  • Resolved
    Resolved
    This incident has been resolved.
  • Investigating
    Investigating
    We are currently investigating this incident.

May 2025

X (fka Twitter) API experiencing downtime
  • Resolved
    Resolved
    This incident has been resolved.
  • Monitoring
    Monitoring

    We are monitoring the Twitter downtime that has been reported: https://downdetector.com/status/twitter/.

  • Investigating
    Investigating

    We are currently investigating this incident with X.

Degraded performance on batch users endpoint
  • Resolved
    Resolved

    This incident has been resolved.

    A database change caused our batch fetching of users to slow down. Fetching user details by ID was not affected. A fix has been deployed and we are monitoring.

  • Investigating
    Investigating

    We are currently investigating an issue causing high latency on our batch users endpoint (GET /api/v1/users)

Apr 2025

Production impact on APIs
  • Resolved
    Resolved

    This incident is resolved. A database failover caused several core API route requests to fail for a period of roughly 2 minutes.

  • Investigating
    Investigating

    We are continuing to investigate this incident, which lasted approximately two minutes.

Apr 2025 to Jun 2025

Next