Is UrbanPiper down?
Last checked just nowNo incidents right now.
UrbanPiper is operational right now. Last checked just now; the most recent incident resolved 15d ago.
Real-time UrbanPiper status, recent outages, and incident history — pulled directly from UrbanPiper's official status page at https://status.urbanpiper.com every 5 minutes. Pingoru tracks 20 UrbanPiper services and has captured 4 incidents in the last 90 days (99.83% uptime). Get email, Slack, Discord, or webhook alerts the moment UrbanPiper reports a new incident — free for 5 monitors, no credit card.
Recent outages & incidents
Past 90 days- Enterprise POS Integrations
Timeline · 3 updates
- investigating · Jul 16, 2026, 03:24 PM UTC
Status: Investigating POS order relay might be affected Affected components Enterprise POS Integrations (Degraded performance)
- investigating · Jul 16, 2026, 03:33 PM UTC
Status: Investigating Custom POS order relay might be affected Affected components Enterprise POS Integrations (Degraded performance)
- resolved · Jul 16, 2026, 03:54 PM UTC
Status: Resolved The custom pos order backlog issue has been resolved. Affected services are now operating normally. We will continue to monitor closely, but no further impact is expected. Thank you for your patience while we worked through this. Affected components Enterprise POS Integrations (Operational)
Latest: Status: Resolved The custom pos order backlog issue has been resolved. Affected services are now operating normally. We will continue to monitor closely, but no further impact is e…
-
- Order Ingestion
Timeline · 3 updates
- investigating · Jul 01, 2026, 12:04 PM UTC
Status: Investigating Ubereats order failures reported. Team is investigating the issue Affected components Order Ingestion (Degraded performance)
- monitoring · Jul 01, 2026, 02:55 PM UTC
Status: Monitoring Uber Eats returned the error "This endpoint requires at least one of the following scopes: eats.order" while UrbanPiper was fetching orders for relay to POS systems, impacting all stores integrated with Uber Eats. Our investigation identified that the affected stores had been switched to webhook version "0.1", whereas the webhook version was expected to remain unset. As a result, the Uber Eats API required access tokens to include the eats.order scope for requests associated with webhook version "0.1", causing order retrieval requests to fail. We coordinated with the Uber Eats engineering team to roll back the affected stores to their previous webhook configuration. Order processing has now resumed successfully, and we are continuing to monitor the platform. Affected components Order Ingestion (Degraded performance)
- resolved · Jul 01, 2026, 04:01 PM UTC
Status: Resolved An integration issue with Uber Eats during a functionality update caused a temporary misconfiguration that affected order processing. We've resolved it with the Uber Eats team, and orders are now processing normally. This incident is resolved and we're continuing to monitor. Affected components Order Ingestion (Operational)
Latest: Status: Resolved An integration issue with Uber Eats during a functionality update caused a temporary misconfiguration that affected order processing. We've resolved it with the Ub…
-
-
Timeline · 2 updates
- monitoring · May 19, 2026, 07:40 PM UTC
Status: Monitoring Between 12:10 IST and 01:00 IST, there was an issue with orders where item modifiers were missed. A fix has been deployed and the team is now monitoring to ensure ingestion remains stable. We are reviewing affected orders and will follow up individually where needed.
- resolved · May 19, 2026, 08:21 PM UTC
Status: Resolved The issue affecting orders between 12:10 IST and 01:00 IST, where item modifiers were missed, has been fully resolved. Ingestion has been stable since the fix was deployed. We appreciate your patience and apologize for any inconvenience this may have caused.
Latest: Status: Resolved The issue affecting orders between 12:10 IST and 01:00 IST, where item modifiers were missed, has been fully resolved. Ingestion has been stable since the fix was …
-
- Started Jul 16, 2026, 03:54 PM UTC · Resolved Jul 16, 2026, 03:54 PM UTC · —
- Started Jul 01, 2026, 04:01 PM UTC · Resolved Jul 01, 2026, 04:01 PM UTC · —
- Started May 19, 2026, 08:21 PM UTC · Resolved May 19, 2026, 08:21 PM UTC · —