Panora Connect Outage History

Panora Connect is up right now

Panora Connect had 32 outages in the last 2 years totaling 43h 41m of downtime — averaging 1.3 incidents per month.

There were 32 Panora Connect outages since June 27, 2025 totaling 43h 41m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.panora.cc

Minor June 15, 2026

Security Verification Issues

Detected by Pingoru
Jun 15, 2026, 03:05 AM UTC
Resolved
Jun 15, 2026, 03:05 AM UTC
Duration
—
Timeline · 4 updates
  1. investigating Jun 15, 2026, 02:39 AM UTC

    Status: Investigating Following our recent platform update, we are currently experiencing issues with our security verification systems. This is causing certain actions protected behind trust verification to fail.

  2. identified Jun 15, 2026, 02:41 AM UTC

    Status: Identified We've found the source of the disruption and our engineers are already deploying the solution.

  3. monitoring Jun 15, 2026, 02:46 AM UTC

    Status: Monitoring We've rolled out the fix and are actively monitoring to make sure the issue doesn’t return.

  4. resolved Jun 15, 2026, 03:05 AM UTC

    Status: Resolved Service has been restored and the incident is resolved.

Read the full incident report →

Minor June 10, 2026

Activity script downloads are currently unavailable for workspace owners.

Detected by Pingoru
Jun 10, 2026, 04:52 AM UTC
Resolved
Jun 10, 2026, 04:52 AM UTC
Duration
—
Affected: Dashboard
Timeline · 4 updates
  1. investigating Jun 10, 2026, 01:26 AM UTC

    Status: Investigating Our team is now aware of an issue and is actively investigating. Affected components Dashboard (Degraded performance)

  2. identified Jun 10, 2026, 01:40 AM UTC

    Status: Identified We've found the source of the disruption and our engineers are already deploying the solution. Affected components Dashboard (Degraded performance)

  3. monitoring Jun 10, 2026, 02:50 AM UTC

    Status: Monitoring We've rolled out the fix and are actively monitoring to make sure the issue doesn’t return. Affected components Dashboard (Operational)

  4. resolved Jun 10, 2026, 04:52 AM UTC

    Status: Resolved Service has been restored and the incident is resolved. Affected components Dashboard (Operational)

Read the full incident report →

Minor May 26, 2026

Activity Tracking Plan Issues

Detected by Pingoru
May 26, 2026, 09:30 PM UTC
Resolved
May 26, 2026, 09:30 PM UTC
Duration
—
Timeline · 4 updates
  1. investigating May 26, 2026, 02:12 PM UTC

    Status: Investigating We are aware of our free Activity Tracking feature failing with the error of "Plan upgrade required". We are investigating.

  2. identified May 26, 2026, 03:45 PM UTC

    Status: Identified We've found the source of the disruption and our engineers are already deploying the solution.

  3. monitoring May 26, 2026, 07:02 PM UTC

    Status: Monitoring We've rolled out the fix and are actively monitoring to make sure the issue doesn’t return.

  4. resolved May 26, 2026, 09:30 PM UTC

    Status: Resolved Service has been restored and the incident is resolved.

Read the full incident report →

Minor May 17, 2026

Legacy Elite Custom Bot Connection Issues

Detected by Pingoru
May 17, 2026, 11:22 AM UTC
Resolved
May 17, 2026, 11:22 AM UTC
Duration
—
Affected: San Francisco Data CenterAmsterdam Data CenterNew York Data Center
Timeline · 3 updates
  1. investigating May 17, 2026, 10:35 AM UTC

    Status: Investigating We are currently investigating an issue where some Legacy Elite users may be unable to complete custom bot connections. Our team is actively looking into the cause and working toward a resolution. We apologize for the inconvenience and will provide updates as more information becomes available. Affected components Amsterdam Data Center (Degraded performance) New York Data Center (Degraded performance) San Francisco Data Center (Degraded performance)

  2. monitoring May 17, 2026, 11:09 AM UTC

    Status: Monitoring We've rolled out the fix and are actively monitoring to make sure the issue doesn’t return. Affected components Amsterdam Data Center (Operational) New York Data Center (Operational) San Francisco Data Center (Operational)

  3. resolved May 17, 2026, 11:22 AM UTC

    Status: Resolved Service has been restored and the incident is resolved. Affected components Amsterdam Data Center (Operational) New York Data Center (Operational) San Francisco Data Center (Operational)

Read the full incident report →

Minor May 16, 2026

Affiliate Program Workspaces unable to create custom bots

Detected by Pingoru
May 16, 2026, 12:45 AM UTC
Resolved
May 16, 2026, 12:45 AM UTC
Duration
—
Timeline · 4 updates
  1. investigating May 16, 2026, 12:18 AM UTC

    Status: Investigating Our team is now aware of an issue and is actively investigating.

  2. identified May 16, 2026, 12:25 AM UTC

    Status: Identified We've found the source of the disruption and our engineers are already deploying the solution.

  3. monitoring May 16, 2026, 12:35 AM UTC

    Status: Monitoring We've rolled out the fix and are actively monitoring to make sure the issue doesn’t return.

  4. resolved May 16, 2026, 12:45 AM UTC

    Status: Resolved Service has been restored and the incident is resolved.

Read the full incident report →

Minor May 15, 2026

Application Center Restriction Errors

Detected by Pingoru
May 15, 2026, 06:25 AM UTC
Resolved
May 15, 2026, 06:25 AM UTC
Duration
—
Affected: Ranking Centers
Timeline · 5 updates
  1. investigating May 15, 2026, 06:07 AM UTC

    Status: Investigating Our team is now aware of an issue and is actively investigating. Affected components Ranking Centers (Full outage)

  2. identified May 15, 2026, 06:12 AM UTC

    Status: Identified We've found the source of the disruption and our engineers are already deploying the solution. Affected components Ranking Centers (Full outage)

  3. monitoring May 15, 2026, 06:15 AM UTC

    Status: Monitoring We've rolled out the fix and are actively monitoring to make sure the issue doesn’t return. Affected components Ranking Centers (Full outage)

  4. investigating May 15, 2026, 06:16 AM UTC

    Status: Investigating We are still attempting to fix the problem. Affected components Ranking Centers (Full outage)

  5. resolved May 15, 2026, 06:25 AM UTC

    Status: Resolved Service has been restored and the incident is resolved. Affected components Ranking Centers (Operational)

Read the full incident report →

Minor May 14, 2026

Customer Support Chatting Issues

Detected by Pingoru
May 14, 2026, 02:17 AM UTC
Resolved
May 14, 2026, 02:17 AM UTC
Duration
—
Affected: Dashboard
Timeline · 3 updates
  1. investigating May 13, 2026, 11:17 PM UTC

    Status: Investigating Our team is now aware of an issue and is actively investigating. Affected components Dashboard (Degraded performance)

  2. identified May 13, 2026, 11:38 PM UTC

    Status: Identified We've found the source of the disruption and our engineers are already deploying the solution. Affected components Dashboard (Degraded performance)

  3. resolved May 14, 2026, 02:17 AM UTC

    Status: Resolved Service has been restored and the incident is resolved. Affected components Dashboard (Operational)

Read the full incident report →

Minor May 9, 2026

Service Disruption

Detected by Pingoru
May 09, 2026, 12:18 AM UTC
Resolved
May 09, 2026, 12:18 AM UTC
Duration
—
Affected: DashboardAuthentication ServiceAccount SessionsVerificationCommand ProcessingTask QueueSchedulerWebhooks
Timeline · 2 updates
  1. investigating May 08, 2026, 07:47 PM UTC

    Status: Investigating We are currently experiencing a service disruption affecting authentication and other platform features. This is caused by an ongoing worldwide outage with Discord, which we rely on for core functionality. Our team is actively monitoring the situation. No action is required on your end. We will provide updates as Discord restores service. We apologize for the inconvenience. Affected components Command Processing (Full outage) Account Sessions (Full outage) Verification (Full outage) Task Queue (Full outage) Authentication Service (Full outage) Dashboard (Full outage) Scheduler (Full outage) Webhooks (Full outage)

  2. resolved May 09, 2026, 12:18 AM UTC

    Status: Resolved Service has been restored and the incident is resolved. Affected components Account Sessions (Operational) Verification (Operational) Task Queue (Operational) Authentication Service (Operational) Dashboard (Operational) Scheduler (Operational) Webhooks (Operational) Command Processing (Operational)

Read the full incident report →

Minor May 1, 2026

Beta Platform Outage

Detected by Pingoru
May 01, 2026, 02:29 PM UTC
Resolved
May 01, 2026, 02:29 PM UTC
Duration
—
Affected: Dashboard
Timeline · 3 updates
  1. investigating May 01, 2026, 05:41 AM UTC

    Status: Investigating The Panora beta website is currently experiencing an internal crash and the platform is unavailable. Our team is actively investigating the issue. We apologize for the inconvenience and will provide updates as soon as possible. Affected components Dashboard (Full outage)

  2. identified May 01, 2026, 05:53 AM UTC

    Status: Identified We've found the source of the disruption and our engineers are already deploying the solution. Affected components Dashboard (Full outage)

  3. resolved May 01, 2026, 02:29 PM UTC

    Status: Resolved Service has been restored and the incident is resolved. Affected components Dashboard (Operational)

Read the full incident report →

Minor April 28, 2026

Discord Outage Impacting Panora Services

Detected by Pingoru
Apr 28, 2026, 09:19 PM UTC
Resolved
Apr 28, 2026, 09:19 PM UTC
Duration
—
Affected: DashboardAuthentication ServiceAccount SessionsVerification
Timeline · 2 updates
  1. investigating Apr 28, 2026, 07:37 PM UTC

    Status: Investigating We are currently experiencing service disruptions due to an ongoing outage with Discord. This may impact features such as: • Authentication • Access to our Discord server • Any integrations relying on Discord services Our systems are operating normally otherwise, and we are actively monitoring the situation. Services will automatically return to normal once Discord resolves the issue. Affected components Authentication Service (Partial outage) Dashboard (Partial outage) Account Sessions (Partial outage) Verification (Partial outage)

  2. resolved Apr 28, 2026, 09:19 PM UTC

    Status: Resolved Service has been restored and the incident is resolved. Affected components Dashboard (Operational) Account Sessions (Operational) Verification (Operational) Authentication Service (Operational)

Read the full incident report →

Minor April 4, 2026

Main Website Outage

Detected by Pingoru
Apr 04, 2026, 01:56 AM UTC
Resolved
Apr 04, 2026, 01:56 AM UTC
Duration
—
Affected: Main Website
Timeline · 4 updates
  1. investigating Apr 04, 2026, 01:16 AM UTC

    Status: Investigating Our team is now aware of an issue and is actively investigating. Affected components Main Website (Full outage)

  2. identified Apr 04, 2026, 01:20 AM UTC

    Status: Identified We've found the source of the disruption and our engineers are already deploying the solution. Affected components Main Website (Full outage)

  3. monitoring Apr 04, 2026, 01:48 AM UTC

    Status: Monitoring We've rolled out the fix and are actively monitoring to make sure the issue doesn’t return. Affected components Main Website (Operational)

  4. resolved Apr 04, 2026, 01:56 AM UTC

    Status: Resolved Service has been restored and the incident is resolved. Affected components Main Website (Operational)

Read the full incident report →

Minor March 20, 2026

Email Delivery Issues

Detected by Pingoru
Mar 20, 2026, 05:33 AM UTC
Resolved
Mar 20, 2026, 05:33 AM UTC
Duration
—
Timeline · 3 updates
  1. identified Mar 20, 2026, 02:09 AM UTC

    Status: Identified During a recent development test, we ran into an API flaw that unintentionally flooded our email provider. As a result, our company email account has been temporarily limited. We’ve already contacted our provider and are currently waiting for them to revert the spam flag and restore normal functionality. Until this is resolved, emails sent from our domains may fail to deliver. We’ll keep you updated as soon as things are back to normal.

  2. monitoring Mar 20, 2026, 05:21 AM UTC

    Status: Monitoring The team has reached out and confirmed no issues. We are recovering.

  3. resolved Mar 20, 2026, 05:33 AM UTC

    Status: Resolved Service has been restored and the incident is resolved.

Read the full incident report →

Minor March 18, 2026

Roblox Group Update Impacting Ranking Commands

Detected by Pingoru
Mar 18, 2026, 06:32 PM UTC
Resolved
Mar 18, 2026, 06:32 PM UTC
Duration
—
Timeline · 4 updates
  1. investigating Mar 18, 2026, 06:15 PM UTC

    Status: Investigating A recent Roblox update to groups has caused issues with ranking commands across our bots. Our team is actively investigating and working on a fix. We appreciate your patience.

  2. identified Mar 18, 2026, 06:20 PM UTC

    Status: Identified We've found the source of the disruption and our engineers are already deploying the solution.

  3. monitoring Mar 18, 2026, 06:31 PM UTC

    Status: Monitoring We've rolled out the fix and are actively monitoring to make sure the issue doesn’t return.

  4. resolved Mar 18, 2026, 06:32 PM UTC

    Status: Resolved Service has been restored and the incident is resolved.

Read the full incident report →

Minor March 8, 2026

Custom Bot Creation Experiencing Issues

Detected by Pingoru
Mar 08, 2026, 06:11 PM UTC
Resolved
Mar 08, 2026, 06:11 PM UTC
Duration
—
Timeline · 4 updates
  1. investigating Mar 08, 2026, 05:35 PM UTC

    Status: Investigating Our team is now aware of an issue and is actively investigating.

  2. identified Mar 08, 2026, 05:45 PM UTC

    Status: Identified We've found the source of the disruption and our engineers are already deploying the solution.

  3. monitoring Mar 08, 2026, 06:08 PM UTC

    Status: Monitoring We've rolled out the fix and are actively monitoring to make sure the issue doesn’t return.

  4. resolved Mar 08, 2026, 06:11 PM UTC

    Status: Resolved Service has been restored and the incident is resolved.

Read the full incident report →

Minor February 9, 2026

US Region Service Disruption

Detected by Pingoru
Feb 09, 2026, 05:00 PM UTC
Resolved
Feb 09, 2026, 05:00 PM UTC
Duration
—
Timeline · 5 updates
  1. investigating Feb 09, 2026, 04:29 PM UTC

    Status: Investigating Our team is now aware of an issue and is actively investigating.

  2. investigating Feb 09, 2026, 04:35 PM UTC

    Status: Investigating The public API is now unreachable. We are working on restoring services as soon as possible.

  3. identified Feb 09, 2026, 04:41 PM UTC

    Status: Identified We've found the source of the disruption and our engineers are already deploying the solution.

  4. monitoring Feb 09, 2026, 04:51 PM UTC

    Status: Monitoring We've rolled out the fix and are actively monitoring to make sure the issue doesn’t return.

  5. resolved Feb 09, 2026, 05:00 PM UTC

    Status: Resolved Service has been restored and the incident is resolved.

Read the full incident report →