Kintag Status Page - Notice history

All systems operational

Kintag → Web - Operational

100.0% uptime
2026-09-01 · 100.0%-10-01 · 100.0%-11-30 · 100.0%
2026-09-01
2026-10-01
2026-11-30

Kintag → Web Probe - Operational

100.0% uptime
2026-09-01 · 100.0%-10-01 · 100.0%-11-30 · 100.0%
2026-09-01
2026-10-01
2026-11-30

Kintag → DNS - Operational

100.0% uptime
2026-09-01 · 100.0%-10-01 · 100.0%-11-30 · 100.0%
2026-09-01
2026-10-01
2026-11-30

Kintag → DNS Alternate - Operational

100.0% uptime
2026-09-01 · 100.0%-10-01 · 100.0%-11-30 · 100.0%
2026-09-01
2026-10-01
2026-11-30

Kintag → Backup - Operational

100.0% uptime
2026-09-01 · 100.0%-10-01 · 100.0%-11-30 · 100.0%
2026-09-01
2026-10-01
2026-11-30

Vercel → CDN → IAD1 - Washington DC, USA - Operational

Vercel → TLS Certificates - Operational

Vercel → Functions - Operational

Vercel → Firewall - Operational

Supabase → Compute capacity → us-east-2 - Operational

Supabase → Connection Pooler - Operational

Supabase → API Gateway - Operational

Supabase → Database - Operational

Supabase → Auth - Operational

Resend → Email Sending → Single Email - Operational

Resend → General API - Operational

Cloudflare → Cloudflare Sites and Services → Email Routing - Operational

Cloudflare → Cloudflare Sites and Services → Authoritative DNS - Operational

Cloudflare → Cloudflare Sites and Services → Turnstile - Operational

Notice history

View current status

2026-11-01

No notices reported this month

2026-10-01

2026-09-01

Intermittent latency in Eastern US
ResolvedDegraded performance163 hours 49 minutes
  • ResolvedUTC

    A fix for this issue has been implemented and our data shows previous impacted users have recovered.

  • MonitoringUTC

    A fix for this issue has been implemented and our data shows recovery for users on projects that have previously been affected. We expect this situation to be resolved, but will keep monitoring for a while until fully resolving this incident.

  • UpdateUTC

    While we have observed significant improvement in rates of high latency, we note that some users are still experiencing issues during peak Eastern US business hours. We continue to work with our networking partners to isolate and resolve any lingering sources of high latency. We recognize that this is a longstanding issue and appreciate the patience of affected customers. We will continue to share additional updates here as soon as they are available.

  • UpdateUTC

    Our networking partners have implemented a mitigation to the latency issue at the problematic PoP in the Eastern US, and we have since observed significant improvement in rates of high latency across the region. We are continuing to work with those partners to isolate any additional root causes of latency and improve the reliability of our networking infrastructure across the region.

  • UpdateUTC

    We are seeing signs of improvement and are continuing to work alongside our networking partners towards a resolution.
    We will provide another update as more information becomes available.

  • UpdateUTC

    We're continuing to coordinate with our networking partners to deliver a permanent resolution.
    We will provide updates as soon as they're available.

  • UpdateUTC

    We are working with our networking partners on a permanent fix.

    While we do not have an estimated resolution time, we will share updates here as they become available.

  • UpdateUTC

    A mitigation for this issue was applied earlier today, but we do not have sufficient evidence to conclude that the mitigation resulted in improvement to this eastern US latency issue. We have tied the issue to a particular PoP, and we are continuing to work with our networking partners to bring this issue to a final resolution. We will provide another update within 4 hours, if not before. We appreciate your patience.

  • UpdateUTC

    We are continuing our work to fix this latency issue, which has been observed to impact clients connecting to Supabase Projects from the eastern United States. These clients may include servers and serverless functions located in that geographical region, regardless of the region in which the Project is hosted.

  • IdentifiedUTC

    We have identified an issue with increased latency for clients in the eastern US during spikes caused by bursty traffic. This is most noticeable during EDT working hours around the :00 and :30 hour marks.

    We are actively working on a fix. We will provide updates as the fix is implemented.

Project Lifecycle Issues in eu-west-1
ResolvedPartial outage2 hours 1 minute
  • ResolvedUTC

    This incident has been resolved.

  • MonitoringUTC

    We are continuing to monitor to ensure ongoing stability.

  • UpdateUTC

    The remaining projects have now been brought back up, and we have no projects remaining on the unhealthy underlying hardware in the upstream infrastructure. We are monitoring to ensure ongoing stability.

  • UpdateUTC

    Most projects have been brought back up, and the team is working on the remaining projects, which should be completed soon.

    This issue was related to specific underlying hardware in the region, so this was isolated to only projects on that hardware. Project lifecycle operations (restarts, upgrades, etc) broadly across the region remain available.

  • UpdateUTC

    All projects affected by the upstream infrastructure issues, and mitigation efforts are underway internally. These affected projects will be brought back up on new hardware as quickly as possible.

  • IdentifiedUTC

    We have isolated the scope of the problem to a specific upstream incident. We are working to address the upstream incident and determine mitigations.

  • InvestigatingUTC

    We are investigating project lifecycle operation issues in eu-west-1.

Previous

2026-09-01 to 2026-11-01

Next