PostgresAI / DBLab - Notice history

All systems operational

Platform/Console - Operational

100% - uptime
Jan 2025 · 99.64%Feb · 100.0%Mar · 99.78%

Previous page

Next page

Jan 2025
Feb 2025
Mar 2025

PostgresAI Bot (alpha) - Operational

99% - uptime
Jan 2025 · 96.08%Feb · 100.0%Mar · 99.78%

Previous page

Next page

Jan 2025
Feb 2025
Mar 2025

Website - Operational

100% - uptime
Jan 2025 · 99.89%Feb · 100.0%Mar · 99.91%

Previous page

Next page

Jan 2025
Feb 2025
Mar 2025

DBLab Demo Main - Operational

100% - uptime
Jan 2025 · 100.0%Feb · 100.0%Mar · 99.94%

Previous page

Next page

Jan 2025
Feb 2025
Mar 2025

DBLab Demo Branching - Operational

100% - uptime
Jan 2025 · 100.0%Feb · 100.0%Mar · 100.0%

Previous page

Next page

Jan 2025
Feb 2025
Mar 2025

Third Party: Stripe → Stripe API - Operational

Third Party: OpenAI → API - Operational

Third Party: GitLab → undefined - Operational

Third Party: ReadMe → ReadMe Hubs - Degraded performance

Third Party: Google Cloud Platform → Google Compute Engine - Operational

Third Party: Google Cloud Platform → Google Kubernetes Engine - Operational

Third Party: Google Cloud Platform → Google Cloud Storage - Operational

Third Party: SendGrid → Mail Sending → API v3 - Operational

Third Party: Intercom → Intercom Web Application - Operational

Third Party: Slack → Slack Apps/Integrations/APIs - Operational

Third Party: Slack → Slack Login/SSO - Operational

Third Party: Slack → Slack Messaging - Operational

Third Party: Slack → Slack Notifications - Operational

Third Party: Zoom → Zoom Meetings → Zoom Meetings - Operational

Third Party: Cloudflare → Cloudflare Sites and Services → DNS Root Servers - Operational

Third Party: Cloudflare → Cloudflare Sites and Services → SSL Certificate Provisioning - Operational

Third Party: Cloudflare → Cloudflare Sites and Services → Network - Operational

Third Party: Cloudflare → Cloudflare Sites and Services → CDN/Cache - Operational

Notice history

Mar 2025

Major outage
  • Resolved
    Resolved
    This incident has been resolved.
  • Monitoring
    Monitoring

    We implemented a fix and are currently monitoring the result.

    The issue was two-sided:
    1) GKE nodes migration caused pod recreation and Postgres failovers
    2) A manual mistake made on 2024-09-28, when reconfiguring backups, we left an extra .history file in pg_wal, corresponding to a timeline that the cluster reached today; this blocked the recover process. Deteling that history file, we unblocked it.

  • Investigating
    Investigating
    We are currently investigating this incident.
Console and Website N/A
  • Resolved
    Resolved
    This incident has been resolved.
  • Monitoring
    Monitoring
    We implemented a fix and are currently monitoring the result.
  • Investigating
    Investigating
    We are currently investigating this incident.

Feb 2025

No notices reported this month

Jan 2025

AI assistant outage
  • Resolved
    Resolved
    This incident has been resolved.
  • Monitoring
    Monitoring
    We implemented a fix and are currently monitoring the result.
  • Investigating
    Investigating
    We are currently investigating this incident.
Major outage
  • Resolved
    Resolved
    This incident has been resolved.
  • Identified
    Identified
    We are continuing to work on a fix for this incident.
  • Monitoring
    Monitoring
    We implemented a fix and are currently monitoring the result.
  • Investigating
    Investigating
    We are currently investigating this incident.
Backend outage
  • Resolved
    Resolved
    This incident has been resolved.
  • Monitoring
    Monitoring
    We implemented a fix and are currently monitoring the result.
  • Investigating
    Investigating
    We are currently investigating this incident.

Jan 2025 to Mar 2025

Next