User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
aiesec.org · Cloud & developer
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
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.
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.
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.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last checked 40 min ago. Last stored result reached it in 127 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 22 | 0 | 0.0 | 122 ms | 0 |
| Tue 00 | 0 | 0.0 | 51 ms | 0 |
| Tue 02 | 0 | 0.0 | 88 ms | 0 |
| Tue 04 | 0 | 0.0 | 53 ms | 0 |
| Tue 07 | 0 | 0.0 | 58 ms | 0 |
| Tue 09 | 0 | 0.0 | 50 ms | 0 |
| Tue 11 | 0 | 0.0 | 35 ms | 0 |
| Tue 13 | 0 | 0.0 | 47 ms | 0 |
| Tue 15 | 0 | 0.0 | 55 ms | 0 |
| Tue 17 | 0 | 0.0 | 265 ms | 0 |
| Tue 20 | 0 | 0.0 | 117 ms | 0 |
| Tue 22 | 0 | 0.0 | 255 ms | 0 |
| Wed 00 | 0 | 0.0 | 84 ms | 0 |
| Wed 02 | 0 | 0.0 | 69 ms | 0 |
| Wed 05 | 0 | 0.0 | 71 ms | 0 |
| Wed 07 | 0 | 0.0 | 62 ms | 0 |
| Wed 09 | 0 | 0.0 | 124 ms | 0 |
| Wed 11 | 0 | 0.0 | 48 ms | 0 |
| Wed 14 | 0 | 0.0 | 185 ms | 0 |
| Wed 16 | 0 | 0.0 | 147 ms | 0 |
| Wed 18 | 0 | 0.0 | 239 ms | 0 |
| Wed 20 | 0 | 0.0 | 125 ms | 0 |
| Wed 22 | 0 | 0.0 | 109 ms | 0 |
| Thu 00 | 0 | 0.0 | 69 ms | 0 |
| Thu 02 | 0 | 0.0 | 175 ms | 0 |
| Thu 04 | 0 | 0.0 | 64 ms | 0 |
| Thu 07 | 0 | 0.0 | 288 ms | 0 |
| Thu 09 | 0 | 0.0 | 173 ms | 0 |
| Thu 11 | 0 | 0.0 | 210 ms | 0 |
| Thu 13 | 0 | 0.0 | 38 ms | 0 |
| Thu 15 | 0 | 0.0 | 61 ms | 0 |
| Thu 17 | 0 | 0.0 | 229 ms | 0 |
| Thu 19 | 0 | 0.0 | 198 ms | 0 |
| Thu 21 | 0 | 0.0 | 278 ms | 0 |
| Thu 23 | 0 | 0.0 | 43 ms | 0 |
| Fri 01 | 0 | 0.0 | 109 ms | 0 |
| Fri 03 | 0 | 0.0 | 96 ms | 0 |
| Fri 05 | 0 | 0.0 | 140 ms | 0 |
| Fri 07 | 0 | 0.0 | 96 ms | 0 |
| Fri 09 | 0 | 0.0 | 125 ms | 0 |
| Fri 10 | 0 | 0.0 | 43 ms | 0 |
| Fri 11 | 0 | 0.0 | 39 ms | 0 |
| Fri 13 | 0 | 0.0 | 52 ms | 0 |
| Fri 15 | 0 | 0.0 | 77 ms | 0 |
| Fri 17 | 0 | 0.0 | 267 ms | 0 |
| Fri 18 | 0 | 0.0 | 136 ms | 0 |
| Fri 19 | 0 | 0.0 | 45 ms | 0 |
| Fri 21 | 0 | 0.0 | 127 ms | 0 |
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 8 days of data so far, so the 90-day numbers fill in over time.
No outages on record for AIESEC yet. Outages of 10 minutes or more get their own page here.
One report per service every 10 minutes from this network. No account.
Get an email when AIESEC goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send AIESEC alerts to Slack, Discord or a webhook — free.
AIESEC is listed in our Cloud & developer category and checked at aiesec.org. Activate your leadership by taking part in one of our programs abroad, in your city, or virtually. Start your leadership journey with AIESEC.
AIESEC publishes an official status page at status.aiesec.org; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with cloud & developer services: API errors, failed deploys or builds, and dashboard or console outages.
Measured uptime from our checks: 100% over 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 102 ms average, 39–267 ms range across 16 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public AIESEC incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
102 ms on average over the last 24 hours (39–267 ms).
Yes, at https://status.aiesec.org.
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 AIESEC here at once, the problem is on AIESEC'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 AIESEC. 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.