Crunchtime Outage History
Crunchtime is up right nowPingoru has recorded 31 incidents for Crunchtime: 31 in the last 12 months and 14 in the last 90 days.
Incidents, newest first
Minor November 19, 2025 Delay in Data Retrieval with Crunchtime Insights and Data Streaming 3h 12m Insights
Started Nov 19, 2025, 04:30 PM UTC· resolved Nov 19, 2025, 07:42 PM UTC
- investigating Nov 19, 2025, 04:30 PM UTC
We are aware of an issue causing a delay in updates to data for Insights and for Data Streaming customers. Any data that was available before the start of this incident will still be available. Our teams are actively investigating. Thank you for your patience while our teams work to get this resolved. An update will be posted within the next hour. ~ The Crunchtime Support Team
- investigating Nov 19, 2025, 06:02 PM UTC
Our development team is continuing to actively investigate. Thank you for your continued patience while our teams work to get this resolved. An update will be posted within the next two hours. ~ The Crunchtime Support Team
- resolved Nov 19, 2025, 07:42 PM UTC
The team has successfully resolved the previously reported delay in data updates. Data is now flowing as expected. Thank you again for your patience while our teams worked through this issue. - The Crunchtime Support team
Minor November 12, 2025 Partial Connex Outage for Cloud-Based POS 1h 45m ConneX
Started Nov 12, 2025, 02:40 PM UTC· resolved Nov 12, 2025, 04:26 PM UTC
- identified Nov 12, 2025, 02:40 PM UTC
We have been experiencing a service disruption from one of our vendors that is causing degraded check and time punch processing for cloud-based POS. Not all cloud-based POS customers are affected, and the degraded processing is intermittant. Check and time punch processing for customers using an on-prem POS is working as expected at this time. We are working with the vendor's engineering team to resolve the service disruption and they will be applying a fix shortly. Once the fix is applied, we will closely monitor the processing queues to confirm that the fix has improved performance and that any missing files are repolled. We apologize for the disruption in service and will continue to provide updates throughout the day.
- identified Nov 12, 2025, 03:45 PM UTC
While customers using an on-prem POS are not directly affected by the service disruption, those performance problems may have caused polling for on-prem customers to be delayed preventatively in the vendor's system. We apologize for any delays, and we are seeing current day sales and labor data being polled for on-prem now. The data should catch up within the next few polling cycles, but please reach out to Support with any concerns.
- resolved Nov 12, 2025, 04:26 PM UTC
Our monitoring of the processing queues has shown greatly improved performance and current sales and labor data being polled as expected for both cloud-based and on-prem POS. The service disruption has been resolved by the applied fix, but we will continue to monitor the queues to confirm there are no performance issues. We apologize again for the disruption and please reach out to Support if you have any concerns.
Major November 5, 2025 Net Chef Downtime 22h 25m
Started Nov 05, 2025, 04:56 PM UTC· resolved Nov 06, 2025, 03:21 PM UTC
- investigating Nov 05, 2025, 04:56 PM UTC
We are currently experiencing an issue with Net-Chef services. Select customers may experience outage on the Net-Chef platform. Our technical teams are actively investigating, we will provide an update within the hour.
- investigating Nov 05, 2025, 06:01 PM UTC
Our technical teams are actively investigating the issue. We will continue to provide updates within the hour.
- investigating Nov 05, 2025, 07:58 PM UTC
Our technical teams are continuing to investigate this issue. We will reach out with further updates as soon as they are available.
- monitoring Nov 05, 2025, 10:07 PM UTC
A fix has been implemented and we are seeing Net-Chef sites remain stable. Our teams are actively monitoring to ensure sites continue to remain stable.
- resolved Nov 06, 2025, 03:21 PM UTC
The issue has been resolved.