Is Tray.ai down?

Last checked 8m ago
Current status
Tray.ai is up

No incidents right now.

Official status page: https://status.tray.ai · Polled every 5 minutes · 20 components tracked

Tray.ai is operational right now. Last checked 8m ago; the most recent incident resolved 5d ago.

Real-time Tray.ai status, recent outages, and incident history — pulled directly from Tray.ai's official status page at https://status.tray.ai every 5 minutes. Pingoru tracks 20 Tray.ai services and has captured 11 incidents in the last 90 days (99.67% uptime). Get email, Slack, Discord, or webhook alerts the moment Tray.ai reports a new incident — free for 5 monitors, no credit card.

Users who monitor Tray.ai also follow these AI services: Tungsten Automation EMEA Together AI Hugging Face Laserfiche Observe.AI Quest Retell AI Braintrust Cerebras Modal View all 6,000+ providers
Tray.ai uptime 99.67% uptime · past 90 days
Mon Wed Fri
JunJulAugSep
Less More

Recent outages & incidents

Past 90 days
  1. Resolved
    Started Aug 10, 2026, 07:26 PM UTC · Resolved Aug 10, 2026, 11:00 AM UTC
    Timeline · 1 update
    • resolved · Aug 10, 2026, 07:26 PM UTC

      Due to a degradation of application performance, the Billing and Usage page was temporarily unavailable for all regions between approximately 11:00 UTC and 19:00 UTC. Billing and usage has been restored to normal functionality. We apologize for any inconvenience this may have caused. If you have any questions or concerns, please feel free to reach out to [email protected]. Thank you for your patience and understanding.

    Latest: Due to a degradation of application performance, the Billing and Usage page was temporarily unavailable for all regions between approximately 11:00 UTC and 19:00 UTC. Billing and u…

  2. Resolved 2h 42m
    Started Jul 16, 2026, 12:06 PM UTC · Resolved Jul 16, 2026, 02:49 PM UTC
    Workflow Builder App
    Timeline · 5 updates
    • investigating · Jul 16, 2026, 12:06 PM UTC

      We're currently investigating an issue affecting login for users logging in via email verification. Our engineering team is looking into it and working to restore normal service as quickly as possible. We apologise for any inconvenience. If you have any questions in the meantime, please feel free to reach out to [email protected].

    • identified · Jul 16, 2026, 12:28 PM UTC

      We've identified the cause of the issue. Our engineering team is working on a fix and we'll provide a further update shortly. We apologise for any inconvenience. If you have any questions in the meantime, please feel free to reach out to [email protected].

    • identified · Jul 16, 2026, 01:48 PM UTC

      Our engineering team is continuing to work on a fix. In the meantime, affected users can log in via the alternative login page for their region as a workaround: US: https://app.tray.io/v2/login EU: https://app.eu1.tray.io/v2/login AP: https://app.ap1.tray.io/v2/login We apologise for any inconvenience. If you have any questions in the meantime, please feel free to reach out to [email protected].

    • monitoring · Jul 16, 2026, 02:33 PM UTC

      We've applied a fix and login should now be working as expected. We're monitoring the situation closely to ensure the issue is fully resolved. We apologise for any inconvenience. If you have any questions in the meantime, please feel free to reach out to [email protected].

    • resolved · Jul 16, 2026, 02:49 PM UTC

      This incident has been resolved and login is now working as expected. Thank you for your patience. If you have any further questions, please feel free to reach out to [email protected].

    Latest: This incident has been resolved and login is now working as expected. Thank you for your patience. If you have any further questions, please feel free to reach out to support@tray.…

  3. Resolved 2h 53m
    Started Jul 13, 2026, 07:39 PM UTC · Resolved Jul 13, 2026, 10:32 PM UTC
    Other
    Timeline · 4 updates
    • investigating · Jul 13, 2026, 07:39 PM UTC

      On July 13, 2026, starting at 15:20 UTC, Gmail authentications within the US region may encounter retries when refreshing the token, but should eventually succeed. We are currently investigating. Thank you for your patience and understanding. If you have any questions or concerns, please feel free to reach out to [email protected].

    • investigating · Jul 13, 2026, 09:01 PM UTC

      Our engineering teams are continuing to investigate this incident. We will be back with more information as soon as possible. We are very sorry for any inconvenience this incident may cause.

    • identified · Jul 13, 2026, 09:55 PM UTC

      During the investigation, we isolated the impact couple of customers and reached out to those customers. If you did not receive a message from us related to this incident, it is highly unlikely that your organization was impacted by this incident. We have a identified the potential cause and are continuing to investigate. We apologise for any inconvenience this incident may have caused. If you have any questions or concerns, please feel free to reach out to [email protected]. Thank you for your patience and understanding.

    • resolved · Jul 13, 2026, 10:32 PM UTC

      On July 13, 2026, from 15:20 to 19:36 UTC, Gmail authentications within the US region may have encountered token refresh retries that eventually succeeded. The impact was isolated to two customers and we have reached out to those customers. If you did not receive a message related to this incident, your organization should not have been affected. We apologise for any inconvenience this incident may have caused. If you have any questions or concerns, please feel free to reach out to [email protected]. Thank you for your patience and understanding.

    Latest: On July 13, 2026, from 15:20 to 19:36 UTC, Gmail authentications within the US region may have encountered token refresh retries that eventually succeeded. The impact was isolated …

  4. Resolved 45m
    Started Jul 02, 2026, 08:06 AM UTC · Resolved Jul 02, 2026, 08:51 AM UTC
    Workflow Execution
    Timeline · 4 updates
    • investigating · Jul 02, 2026, 08:06 AM UTC

      Starting 7:00 AM UTC on Thursday, July 2, 2026, some customers in the US region may be experiencing issues with scheduled triggers not firing, which is impacting workflow execution. Our team is currently investigating the root cause and working towards a resolution. We will provide further updates as more information becomes available. We apologise for any inconvenience this may cause. If you have any questions or concerns, please feel free to reach out to [email protected]. Thank you for your patience and understanding.

    • identified · Jul 02, 2026, 08:09 AM UTC

      We have identified the issue causing scheduled triggers not to fire, impacting workflow execution in the US region. Our team is currently applying a fix and monitoring the results closely. We will provide further updates as more information becomes available.

    • monitoring · Jul 02, 2026, 08:11 AM UTC

      The fix for the scheduled trigger issue has now taken effect, and all delayed workflow executions have caught up. Our systems have been operating normally since 7:50 AM UTC. We are continuing to monitor the situation closely to ensure stability.

    • resolved · Jul 02, 2026, 08:51 AM UTC

      This incident has now been resolved and all our systems are operational. We apologise for any inconvenience this incident may have caused. If you have any questions or concerns, please feel free to reach out to [email protected]. Thank you for your patience and understanding.

    Latest: This incident has now been resolved and all our systems are operational. We apologise for any inconvenience this incident may have caused. If you have any questions or concerns, pl…

  5. Resolved 39s
    Started Jun 18, 2026, 04:12 PM UTC · Resolved Jun 18, 2026, 04:13 PM UTC
    Workflow ExecutionInsights, Usage and Logs
    Timeline · 2 updates
    • investigating · Jun 18, 2026, 04:12 PM UTC

      Users may be experiencing issues related to project versions across all regions. Our engineering team is currently investigating the issue and working toward a resolution. We apologise for any inconvenience this incident may have caused.

    • resolved · Jun 18, 2026, 04:13 PM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

Outage history

Past 90 days · 5 incidents View full outage history →