Service status
All 5 monitored services are responding.
Everything on this page is measured. A checker on our own infrastructure requests each service once a minute, records what came back, and this page renders those records — including the ones we would rather not show.
Current state
All checks passing
5 of 5 services answered their last check as expected.
Last checked
Checked every 60 seconds, by a probe.
We have been measuring for 26.1 days. Uptime percentages below are computed over that window and no further — where a figure covers less than its column heading it is marked partial, and we would rather show you a short honest record than a long invented one. Checks run from our own application host, over the public internet through our CDN, so this measures the path a visitor takes rather than a loopback that would always look green. Two limits worth knowing: a failure of that host, or of its network, would go unrecorded because the thing doing the recording went with it — and this page is served by one of the applications it monitors, so if you can read it at all, that much is working.
Monitored services
What is checked, and what came back.
Each row is one HTTP request made 60 seconds ago or less. Response time is the complete round trip from our checker, including TLS and the full body.
| Service | Scope | Last response | State |
|---|---|---|---|
| partvps.comhttps://partvps.com/ | The public website: marketing pages, pricing and the order entry points. | 997 msHTTP 200 | Respondingsince 20:02 UTC |
| beta.partvps.comhttps://beta.partvps.com/ | The new storefront and customer portal application. | 776 msHTTP 200 | Respondingsince 05:08 UTC |
| my.partvps.comhttps://my.partvps.com/ | Billing, invoices, tickets and the account panel. | 2579 msHTTP 200 | Respondingsince 16:15 UTC |
| Edge ping endpointhttps://beta.partvps.com/api/edge/ping | The 204 endpoint the site's own latency probe times. A stand-in for request-path health. | 660 msHTTP 204 | Respondingsince 20:02 UTC |
| Billing bridgeloopback → billing engine (read-only call) | The loopback link from the application to the billing engine and its database. A real read is executed each check. | 618 msHTTP 200 | Respondingsince 16:15 UTC |
Measured uptime
Computed from 26.1 days of one-minute checks.
A check counts as up only if the service answered with the status we expect. Every failure counts against the figure, including single-minute blips nobody noticed.
| Service | 24 hours | 7 days | 30 days | Typical response |
|---|---|---|---|---|
| partvps.com | 100%1440 checks | 99.98%9646 checks | 99.97%partial · 26.1 days | 811 msmedian, 1440 checks |
| beta.partvps.com | 100%1440 checks | 99.98%9646 checks | 99.94%partial · 26.1 days | 644 msmedian, 1440 checks |
| my.partvps.com | 100%1440 checks | 100%9646 checks | 99.99%partial · 26.1 days | 2407 msmedian, 1440 checks |
| Edge ping endpoint | 100%1440 checks | 99.97%9646 checks | 99.94%partial · 26.1 days | 463 msmedian, 1440 checks |
| Billing bridge | 100%1440 checks | 100%9646 checks | 100.00%partial · 26.1 days | 439 msmedian, 1440 checks |
Partial means our record is shorter than the column: the percentage is real, but it describes only the 26.1 days we have measured, not a full 7 or 30 days. Nothing here is back-filled or estimated. Raw per-check records are kept for 14 days and the daily rollups they feed for 95 days.
Incident history
Every failed check, grouped into runs.
We do not write these by hand. Any unbroken run of failed checks against one service is an incident and appears below automatically, however brief. Admins are paged after 2 consecutive failures so a single dropped packet does not become an alert — but it still lands in this list and still counts against uptime.
partvps.com
unexpected http 502
Started
Duration
1 min
1 failed checks
beta.partvps.com
unexpected http 502
Started
Duration
1 min
1 failed checks
Edge ping endpoint
unexpected http 502
Started
Duration
1 min
1 failed checks
partvps.com
unexpected http 502
Started
Duration
1 min
1 failed checks
beta.partvps.com
unexpected http 502
Started
Duration
1 min
1 failed checks
Edge ping endpoint
unexpected http 502
Started
Duration
1 min
1 failed checks
Edge ping endpoint
unexpected http 502
Started
Duration
1 min
1 failed checks
partvps.com
unexpected http 502
Started
Duration
1 min
1 failed checks
beta.partvps.com
unexpected http 502
Started
Duration
1 min
1 failed checks
Edge ping endpoint
unexpected http 502
Started
Duration
1 min
1 failed checks
partvps.com
unexpected http 502
Started
Duration
1 min
1 failed checks
beta.partvps.com
unexpected http 502
Started
Duration
1 min
1 failed checks
Edge ping endpoint
unexpected http 502
Started
Duration
1 min
1 failed checks
partvps.com
unexpected http 502
Started
Duration
1 min
1 failed checks
beta.partvps.com
unexpected http 502
Started
Duration
1 min
1 failed checks
Edge ping endpoint
unexpected http 502
Started
Duration
1 min
1 failed checks
Edge ping endpoint
timeout after 10000 ms
Started
Duration
1 min
1 failed checks
beta.partvps.com
unexpected http 404
Started
Duration
1 min
1 failed checks
Edge ping endpoint
unexpected http 404
Started
Duration
1 min
1 failed checks
my.partvps.com
timeout after 10000 ms
Started
Duration
1 min
1 failed checks
beta.partvps.com
timeout after 10000 ms
Started
Duration
2 min
2 failed checks
partvps.com
unexpected http 502
Started
Duration
1 min
1 failed checks
beta.partvps.com
unexpected http 502
Started
Duration
1 min
1 failed checks
Edge ping endpoint
unexpected http 502
Started
Duration
1 min
1 failed checks
partvps.com
timeout after 10000 ms
Started
Duration
3 min
1 failed checks
beta.partvps.com
timeout after 10000 ms
Started
Duration
3 min
1 failed checks
Edge ping endpoint
timeout after 10000 ms
Started
Duration
3 min
1 failed checks
my.partvps.com
timeout after 10000 ms
Started
Duration
4 min
2 failed checks
Billing bridge
timeout after 10000 ms
Started
Duration
4 min
2 failed checks
partvps.com
unexpected http 502
Started
Duration
2 min
2 failed checks
beta.partvps.com
unexpected http 502
Started
Duration
2 min
2 failed checks
Edge ping endpoint
unexpected http 502
Started
Duration
2 min
2 failed checks
partvps.com
unexpected http 502
Started
Duration
1 min
1 failed checks
beta.partvps.com
unexpected http 502
Started
Duration
1 min
1 failed checks
Edge ping endpoint
unexpected http 502
Started
Duration
1 min
1 failed checks
partvps.com
unexpected http 502
Started
Duration
1 min
1 failed checks
beta.partvps.com
unexpected http 502
Started
Duration
1 min
1 failed checks
Edge ping endpoint
unexpected http 502
Started
Duration
1 min
1 failed checks
beta.partvps.com
unexpected http 500
Started
Duration
2 min
2 failed checks
Edge ping endpoint
unexpected http 500
Started
Duration
2 min
2 failed checks
beta.partvps.com
unexpected http 502
Started
Duration
2 min
2 failed checks
Edge ping endpoint
unexpected http 502
Started
Duration
2 min
2 failed checks
beta.partvps.com
unexpected http 502
Started
Duration
2 min
2 failed checks
Edge ping endpoint
unexpected http 502
Started
Duration
2 min
2 failed checks
Regions
We do not have a probe inside a region, so we do not colour one.
Compute, snapshots, daily backups and private networking are available in every region below — there is no reduced-capability location on the list. What we cannot tell you from this page is whether a specific region is healthy right now: our servers there are resold, we operate no always-on endpoint in them, and a green dot we did not measure would be decoration.
Europe
- Frankfurtfra
- Helsinkihel
- Amsterdamams
- Londonlon
- Parispar
- Nurembergnue
- Warsawwaw
- Luxembourglux
- Sinessns
- Madridmad
- Stockholmsto
- Manchesterman
- Milanmil
- Gravelinesgra
- Roubaixrbx
- Strasbourgsbg
- Marseillemrs
- Limburglim
- Eritheri
- Pragueprg
- Viennavie
- Zurichzrh
- Brusselsbru
- Chestercet
Middle East
- Dubaidxb
- Istanbulist
- Tel Avivtlv
Americas
- New Yorknyc
- Ashburnash
- Silicon Valleysfo
- Torontotor
- Vint Hill (VA)vin
- Hillsboro (OR)hil
- Sao Paulogru
- Santiagoscl
- Chicagoord
- Atlantaatl
- Los Angeleslax
- Miamimia
- Seattlesea
- Dallasdfw
- Washingtoniad
- Mexico Citymex
- Beauharnoisbhs
- Denverden
- Palo Altopao
- Honoluluhnl
Asia-Pacific
- Singaporesgp
- Tokyonrt
- Mumbaibom
- Sydneysyd
- Bangaloreblr
- Incheonicn
- Osakaitm
- Hong Konghkg
- Melbournemel
- Tashkenttas
- Seoulsel
- Delhi NCRdel
- Jakartacgk
- Chennaimaa
- Almatyala
- Bakugyd
Africa
- Johannesburgjnb
If a region is affected we name it in words on this page and email the customers with servers in it. In the meantime, the homepage lets your own browser time a public reference host in most of these cities, which is a measurement you can trust because you took it.
The commitment
99.9% availability, backed by credit.
We commit to 99.9% monthly availability for compute and network. That allows roughly 43 minutes of unavailability in a 30-day month. When we miss it, you are owed service credit — the amount and the claim window are written into the agreement rather than left to goodwill.
Scheduled maintenance is announced in advance and does not count against the figure. Anything unannounced does. The figures on this page measure our own platform surfaces; they are not the SLA calculation for your individual server, which is assessed per service against the agreement.
Reporting something
Tell us what you are seeing.
If your service is not behaving and every check on this page is passing, we want to know immediately — it usually means the problem is specific to your server or your route to it, and that is faster to fix, not slower.
- Send to
- [email protected]
- Include
- Region, server identifier, what you ran, what you expected and what happened instead, with timestamps in UTC.
- First reply
- Within one hour, 24 hours a day, for anything down.
- Updates
- During an incident we email affected customers directly, and the run of failed checks appears above on its own. There is no subscription feed to sign up for yet.