Skip to content

Outage tracker / Crisp / In the US

Is Crisp down in the US?

Checks passingin the US, measured from Ashburn and San Jose

All 2 of our probes in the US, in Ashburn and San Jose, read checks passing when they last checked Crisp at Nov 7, 2026, 5:45 PM UTC.

Over the last 24 hours we completed 266 checks from Ashburn and San Jose and 266 answered cleanly, 100.00% availability.

Of the 2 other regions we check Crisp from, all 2 read checks passing right now.

Email me the next time we see Crisp go down

One email when our checks of Crisp fail from two or more distant regions, and one when they pass, after you confirm the address. No account, no card.

This is our own reading from outside. It is not Crisp's official status.

What our Ashburn and San Jose probes measured

AshburnChecks passing142 checks in 24h, 100.00%
San JoseChecks passing124 checks in 24h, 100.00%

Last checked Nov 7, 2026, 5:45 PM UTC.

Crisp from Ashburn and San Jose over the last 30 days

Over the last 30 days, Crisp answered our Ashburn probe in 1,009 ms on average, and 1 check in 20 took longer than 1,480 ms.

Over the last 30 days, Crisp answered our San Jose probe in 1,350 ms on average, and 1 check in 20 took longer than 1,959 ms.

Ranked by average response time across the 4 cities we check Crisp from, Ashburn 2nd, San Jose 3rd; Frankfurt was fastest at 657 ms and Tokyo slowest at 1,953 ms.

From Ashburn and San Jose we ran 1,318 checks of Crisp in 6 days, and 1,316 answered cleanly: 99.84% availability.

1 of the 6 days had at least one failed check. The weakest was Nov 3 (UTC), at 99.19% across 249 checks.

In Ashburn local time (EST), Crisp was slowest around 12 AM, at 1,229 ms on average over the last 14 days, and quickest around 9 AM, at 858 ms.

Day (UTC)ChecksAvailabilityAverage response
Sat, Nov 7200100.00%1,245 ms
Fri, Nov 6256100.00%1,139 ms
Thu, Nov 5253100.00%1,168 ms
Wed, Nov 4254100.00%1,178 ms
Tue, Nov 324999.19%1,121 ms
Mon, Nov 2106100.00%1,095 ms

Crisp outages measured from the US

Our Ashburn and San Jose probes measured no confirmed Crisp outage in the last 90 days.

How the other regions read right now

Of the 2 other regions we check Crisp from, all 2 read checks passing right now.

Probe cityRight nowLast 24h
FrankfurtChecks passing100.00% of 118 checks
TokyoChecks passing100.00% of 70 checks

Other countries we check Crisp from

How we measured this

The US readings on this page come from RealUptime's own Ashburn and San Jose probes against Crisp's public endpoints. They are not user reports, and they are not Crisp's own status page.

See Crisp's full check readings, the 90-day history by region, or the outage tracker methodology.

The US readings here are taken from that country and show the time of the last one, but Crisp has not yet accumulated enough continuous history for us to publish this page to search engines.

Check your own site from Ashburn

This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.

Start monitoring your own servers

Run a service people depend on? Give them a status page on your own domain, checked every minute from six regions, for $9 a month. Get Starter