Skip to main content
Routific logo

Is Routific Down?

No — Routific is up
Routific's status page
Operational · no open incidents
FlareWarden checks
Website reachable · 8 of 8 regions · 211 ms

Right now

The verdict is the worse of these two. How we decide

Routific's status page

status.routific.com · read · checked every 3 minutes

Operational
Routific's components, as its status page reports them
ComponentStatus
Routific APIOperational
Routific SaaS productOperational
Driver Mobile AppOperational
New RoutificOperational
AWS cloudFrontOperational
Twilio SMSOperational
Stripe APIOperational
Mandrill US EastOperational
RedisToGo APIOperational
Routific Shopify ServiceOperational
Routific NotificationsOperational
1 location All operational

FlareWarden checks

routific.com from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours

Reachable
Regions up
8 of 8
Response
211 ms
Checked

By region

  • Amsterdam reachable, 238 ms
  • Dallas reachable, 192 ms
  • Frankfurt reachable, 149 ms
  • Newark reachable, 147 ms
  • Paris reachable, 160 ms
  • Stockholm reachable, 373 ms
  • São Paulo reachable, 198 ms
  • Toronto reachable, 232 ms
Timing by region
Connection timing for each region that loaded the page
RegionDNSTCPTLSTTFB
Amsterdam136 ms3 ms16 ms220 ms
Dallas119 ms2 ms10 ms171 ms
Frankfurt70 ms3 ms14 ms135 ms
Newark71 ms3 ms10 ms128 ms
Paris73 ms2 ms9 ms148 ms
Stockholm138 ms16 ms26 ms284 ms
São Paulo134 ms1 ms10 ms178 ms
Toronto154 ms2 ms8 ms214 ms
We check that routific.com loads, not every feature behind it. Test it yourself

History

Incidents Routific reported

Since Oct 29, 8 days · from status.routific.com

Incidents
0
Major or critical
0
Median to resolve
—

No incidents reported in this window.

Routific website availability

Measured by FlareWarden · routific.com

Last 7 days
100%
Last 30 days
100%
Last 90 days
100%
Avg response, 30 days
247ms

Last 30 days

8-day clean streak
Oct 7: no data
Oct 8: no data
Oct 9: no data
Oct 10: no data
Oct 11: no data
Oct 12: no data
Oct 13: no data
Oct 14: no data
Oct 15: no data
Oct 16: no data
Oct 17: no data
Oct 18: no data
Oct 19: no data
Oct 20: no data
Oct 21: no data
Oct 22: no data
Oct 23: no data
Oct 24: no data
Oct 25: no data
Oct 26: no data
Oct 27: no data
Oct 28: no data
Oct 29: 100.00% uptime, 16 checks
Oct 30: 100.00% uptime, 32 checks
Oct 31: 100.00% uptime, 32 checks
Nov 1: 100.00% uptime, 32 checks
Nov 2: 100.00% uptime, 32 checks
Nov 3: 100.00% uptime, 32 checks
Nov 4: 100.00% uptime, 32 checks
Nov 5: 100.00% uptime, 32 checks
Oct 7 Today
No downtime Partial Downtime Not measurable No data

Measured by FlareWarden's own checks of routific.com from multiple regions every 6 hours. Routific's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 8 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

What Routific does

Routific plans delivery routes for businesses that run their own local deliveries. Dispatchers import orders, including from Shopify, and Routific works out efficient routes for each driver. Drivers follow them in the Routific driver app, and customers get text and email notifications with tracking links. Developers can also call the Routific API to optimise routes in their own software.

What an outage looks like

Dispatchers cannot sign in and the platform returns errors, as on September 1, 2026, when an incident at Routific's cloud provider affected the app, API, driver app and notifications for about an hour and a half. Driver tracking and notification links fail with authentication errors (August 25). Webhooks stop (August 20), email notifications go out late (July 8), and customer management can fail (June 17).

What to do about it

Check status.routific.com, linked from routific.com, which lists the Routific app, New Routific, the API, the driver app, notifications and the Shopify service, plus upstream providers such as AWS, Twilio SMS and Stripe. After the September 1 incident Routific said retrying should succeed in most cases as service recovered.

Is it down for everyone, or just you?

If this page says Routific is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

Routific outage FAQ

Is Routific down for everyone?
Check status.routific.com, which marks which part of the platform is affected. The last major outage there was on September 1, 2026, when login and much of the platform failed for about an hour and a half because of an incident at Routific's cloud provider. Smaller incidents usually hit one piece, such as webhooks or notifications.
Why aren't my customers getting Routific delivery notifications?
Check the Routific Notifications component and Twilio SMS on status.routific.com. Routific has posted delayed email notifications (July 8, 2026) and authentication errors that broke driver tracking and notification links (August 25). Text notifications also depend on Twilio, so a Twilio incident can delay them while routes and the app work.
Does a Shopify outage affect Routific?
It can affect orders that come from Shopify. Routific lists a Routific Shopify Service component, so check it alongside Shopify's own status if new Shopify orders are not appearing for routing. The Shopify service is reported apart from the main Routific app, so check that row specifically rather than the overall status.
Does an AWS outage affect Routific?
It can. Routific lists AWS CloudFront and AWS ec2-us-east-1 among the services it depends on, and its September 1, 2026 outage was caused by an incident at its cloud infrastructure provider. If AWS reports trouble in us-east-1, watch status.routific.com. The same list includes Twilio SMS, the Stripe API and Mandrill US East.

How we measure this

  • We request Routific's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. Our checks only change their verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where Routific publishes an official status feed we read it too, and the verdict is the worse of what it reports and what our checks see: a major outage of Routific itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. We check the feed every 3 minutes and read it again within minutes of any change to its incidents or components; a reading counts for 45 minutes after the last check that found nothing changed. The availability figures above are our measurement alone.

Get alerted when Routific goes down

We check Routific every 6 hours, and again when you open this page if that was more than 30 minutes ago. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required