Is Skio Down?
- Skio's status page
- Operational · no open incidents
- FlareWarden checks
- Website reachable · 8 of 8 regions · 222 ms
Right now
The verdict is the worse of these two. How we decide
Skio's status page
status.skio.com · read · checked every 3 minutes
| Component | Status |
|---|---|
| Skio Charge Processing | Operational |
| Skio Customer Portal | Operational |
| Skio Merchant Portal | Operational |
| Skio API | Operational |
| Skio Webhooks | Operational |
| Postmark | Operational |
| Twilio SMS (Skio SMS) | Operational |
| Shopify Admin | Operational |
| Shopify API & Mobile | Operational |
| Shopify Checkout | Operational |
| Shopify Storefront | Operational |
| Shopify Third party services | Operational |
FlareWarden checks
skio.com from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours
- Regions up
- 8 of 8
- Response
- 222 ms
- Checked
By region
- Ashburn reachable, 141 ms
- Frankfurt reachable, 90 ms
- Johannesburg reachable, 593 ms
- London reachable, 155 ms
- Los Angeles reachable, 284 ms
- Newark reachable, 157 ms
- São Paulo reachable, 195 ms
- Tokyo reachable, 163 ms
Timing by region
| Region | DNS | TCP | TLS | TTFB |
|---|---|---|---|---|
| Ashburn | 91 ms | 3 ms | 14 ms | 119 ms |
| Frankfurt | 48 ms | 4 ms | 9 ms | 67 ms |
| Johannesburg | 246 ms | 37 ms | 42 ms | 369 ms |
| London | 43 ms | 11 ms | 18 ms | 88 ms |
| Los Angeles | 27 ms | 31 ms | 32 ms | 121 ms |
| Newark | 65 ms | 9 ms | 14 ms | 103 ms |
| São Paulo | 153 ms | 3 ms | 14 ms | 175 ms |
| Tokyo | 112 ms | 5 ms | 10 ms | 138 ms |
History
Incidents Skio reported
Since Oct 29, 8 days · from status.skio.com
- Incidents
- 1
- Major or critical
- 1
- Median to resolve
- 8m
- lasted 8m
major ·
Skio website availability
Measured by FlareWarden · skio.com
- Last 7 days
- 100%
- Last 30 days
- 100%
- Last 90 days
- 100%
- Avg response, 30 days
- 242ms
Last 30 days
8-day clean streakMeasured by FlareWarden's own checks of skio.com from multiple regions every 6 hours. Skio'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 Skio does
Skio runs subscriptions for Shopify stores: it bills recurring orders, gives subscribers a customer portal to manage their subscription, and gives the merchant a dashboard for subscribers, analytics and retention. More than a thousand Shopify brands use it. Because it sits on top of Shopify and sends login codes by email and text, a problem at Shopify, Postmark or Twilio can show up in Skio too.
What an outage looks like
Merchants see errors such as Unable to load customers in the dashboard while billing and customer pages keep working (September 21, 2026). Subscribers cannot reach the customer portal or get stuck on a Verifying Browser error (August 13, 2025), or login code emails stop arriving (July 18, 2025). Analytics dashboards fail to load or show wrong revenue (June 2025) while subscription charges are unaffected.
What to do about it
Check status.skio.com, linked from skio.com, which separates Charge Processing, the Customer Portal, the Merchant Portal, the API and webhooks, and also shows Shopify, Postmark and Twilio SMS. Charge Processing is the row that matters for revenue: most Skio incidents leave billing running. If login codes by email fail, subscribers can still use SMS codes or a password, as Skio noted in July 2025.
Is it down for everyone, or just you?
If this page says Skio 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.
Related services
Skio outage FAQ
Are subscription charges affected when Skio is down?
Does a Shopify outage affect Skio?
Why can't my subscribers log in to the Skio portal?
Is my analytics data wrong in Skio?
How we measure this
- We request Skio'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
403or429means 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 Skio 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 Skio 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 Skio goes down
We check Skio 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