Supabase Vector status: API, auth, latency & outage reports
Supabase Vector appears degraded right now. DownForAI checks Supabase Vector every ~75 minutes across 1 monitored surface, with 0 community reports in the last 24 hours.
DownForAI monitors Supabase Vector via a single endpoint — Supabase Web. Current status: degraded — monitoring signals indicate a partial service issue. Measured uptime over the last 24 hours: 100.0%. Median response time (24 h): 105 ms; p95: 279 ms.
Supabase Vector had 1 tracked incident over the last 30 days. The most recent was logged on September 1, 2026 ("supabase-vector experiencing issues", lasting 3871 min).
Current Status
Having issues?
Help other users by reporting if Supabase Vector is not working for you.
Uptime — last 24h
100.0%Network latency — last 20 probes
Reported symptoms
No user reports for Supabase Vector in the last 24 hours.
How we monitor
DownForAI checks monitored AI service surfaces on a rotating schedule, roughly every 75 minutes per surface, from a single centralized probe infrastructure. For services with an official machine-readable status page, we use that official status signal when available. For other services, we perform a basic public-surface check. Some services block datacenter probes; in those cases we mark them as “Monitoring limited” instead of treating a failed probe as a confirmed outage. Status is classified as Operational, Degraded, or Outage. Network latency (check response time) measures how long the monitored endpoint took to respond to our probe — it is not model inference speed, time-to-first-token, or tokens-per-second performance. We are independent of all providers listed and receive no compensation to report any particular status.
Community Discussion
Still having issues with Supabase Vector?
Let the community know and help others experiencing the same problem.