User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Cloud & developer
pepper.inc · Cloud & developer
Is Pepper down?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Is it just me?
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Your browser → pepper.inc—
Your browser → us—
Our checksReaching it
Official · ReportsAll clear · Near baseline
DNS (1.1.1.1 · Google)—
Your provider—
Connection—
Upstream—
Press Run testYour browser tests the site, us, and two public DNS resolvers. We never store your IP; only anonymous counts by network and region.
Live outage map
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses. Every report with a known place can appear on the map. Updates every minute.
What's broken
Recent reports
Each row is a time, a coarse place, and a problem type from a new report. Optional notes stay private. Places with fewer than 3 reports in the last 8 days are shown without a location.
No public reports yet.
Our checks
Reaching it
Last checked 36 min ago. Last stored result reached it in 148 ms.
Official status
All clear
All systems operational Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 13 | 0 | 0.0 | 159 ms | 0 |
| Mon 15 | 0 | 0.0 | 194 ms | 0 |
| Mon 17 | 0 | 0.0 | 208 ms | 0 |
| Mon 19 | 0 | 0.0 | 240 ms | 0 |
| Mon 21 | 0 | 0.0 | 102 ms | 0 |
| Mon 23 | 0 | 0.0 | 220 ms | 0 |
| Tue 01 | 0 | 0.0 | 258 ms | 0 |
| Tue 03 | 0 | 0.0 | 135 ms | 0 |
| Tue 06 | 0 | 0.0 | 104 ms | 0 |
| Tue 08 | 0 | 0.0 | 128 ms | 0 |
| Tue 10 | 0 | 0.0 | 126 ms | 0 |
| Tue 12 | 0 | 0.0 | 127 ms | 0 |
| Tue 14 | 0 | 0.0 | 92 ms | 0 |
| Tue 16 | 0 | 0.0 | 172 ms | 0 |
| Tue 19 | 0 | 0.0 | 91 ms | 0 |
| Tue 21 | 0 | 0.0 | 166 ms | 0 |
| Tue 23 | 0 | 0.0 | 192 ms | 0 |
| Wed 01 | 0 | 0.0 | 210 ms | 0 |
| Wed 04 | 0 | 0.0 | 296 ms | 0 |
| Wed 06 | 0 | 0.0 | 172 ms | 0 |
| Wed 08 | 0 | 0.0 | 2174 ms | 0 |
| Wed 10 | 0 | 0.0 | 209 ms | 0 |
| Wed 13 | 0 | 0.0 | 143 ms | 0 |
| Wed 15 | 0 | 0.0 | 190 ms | 0 |
| Wed 17 | 0 | 0.0 | 244 ms | 0 |
| Wed 19 | 0 | 0.0 | 188 ms | 0 |
| Wed 21 | 0 | 0.0 | 114 ms | 0 |
| Wed 23 | 0 | 0.0 | 204 ms | 0 |
| Thu 02 | 0 | 0.0 | 212 ms | 0 |
| Thu 04 | 0 | 0.0 | 167 ms | 0 |
| Thu 06 | 0 | 0.0 | 173 ms | 0 |
| Thu 08 | 0 | 0.0 | 139 ms | 0 |
| Thu 10 | 0 | 0.0 | 3425 ms | 0 |
| Thu 12 | 0 | 0.0 | 115 ms | 0 |
| Thu 14 | 0 | 0.0 | 168 ms | 0 |
| Thu 16 | 0 | 0.0 | 1107 ms | 0 |
| Thu 19 | 0 | 0.0 | 193 ms | 0 |
| Thu 21 | 0 | 0.0 | 185 ms | 0 |
| Thu 22 | 0 | 0.0 | 120 ms | 0 |
| Fri 01 | 0 | 0.0 | 70 ms | 0 |
| Fri 03 | 0 | 0.0 | 174 ms | 0 |
| Fri 05 | 0 | 0.0 | 164 ms | 0 |
| Fri 07 | 0 | 0.0 | 176 ms | 0 |
| Fri 09 | 0 | 0.0 | 269 ms | 0 |
| Fri 11 | 0 | 0.0 | 127 ms | 0 |
| Fri 13 | 0 | 0.0 | 118 ms | 0 |
| Fri 15 | 0 | 0.0 | 180 ms | 0 |
| Fri 17 | 0 | 0.0 | 148 ms | 0 |
Reliability
100%Uptime · 30 days
100%Uptime · 90 days
0 / 0Outages · 30 / 90 days
—Average outage
100% uptime · No user reports in the last 24h
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 7 days of data so far, so the 90-day numbers fill in over time.
Embed this status: free live Pepper badge
Free, no iframe or script. Updates every minute and links back here. More options on the embed page · badge docs · JSON · MCP server
Past outages
No outages on record for Pepper yet. Outages of 10 minutes or more get their own page here.
Having trouble with Pepper?
One report per service every 10 minutes from this network. No account.
Follow Pepper
Get an email when Pepper goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Pepper alerts to Slack, Discord or a webhook — free.
About Pepper
We track Pepper (pepper.inc) as part of the Cloud & developer group. The only Human + Agentic Al organic growth engine that owns strategy, technology, and talent to drive brand visibility and qualified leads for enterprises.
Pepper publishes an official status page at status.pepper.inc; when we can read it, its incident level is folded into the status shown here.
Common problems for cloud & developer services: API errors, failed deploys or builds, and dashboard or console outages.
Measured uptime from our checks: 100% over 7 days of checks. No public incidents logged since monitoring began 7 days ago.
Response time over the last 24 hours: 153 ms average, 40–269 ms range across 13 successful checks.
Questions
Is Pepper down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was Pepper last down?
We have not recorded a public Pepper incident since monitoring began 7 days ago.
What is Pepper's uptime?
From our own checks: 100% over 7 days of checks.
How fast does Pepper respond?
153 ms on average over the last 24 hours (40–269 ms).
Does Pepper have an official status page?
Yes, at https://status.pepper.inc.
Pepper not working for me but the status is fine. What now?
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For cloud & developer services, watch for API errors, failed deploys or builds, and dashboard or console outages. If many people report Pepper here at once, the problem is on Pepper's side.
How we detect and verify outages · Dispute this report · We review disputes within 24 hours.
Community comments
Share what you are seeing with Pepper. No account needed. Comments are public, separate from outage reports. Do not include personal information.
No links or domains. 3 comments per service and 6 total per hour, per device and network. New contributors get one visible comment; further comments wait for review.