Is It Down? — vodacom.co.za
UP
Current
200
HTTP Code
987
Response ms
100%
Uptime (20)
0
Outages
Response Time — Last 20 Checks
UP DOWN
Recent Checks (Last 20 Pings)
| Time (America/New_York) | Status | HTTP Code | Response (ms) | |
|---|---|---|---|---|
| 07:58:32 · 15.03.2026 | UP | 200 | 987 | |
| 00:52:03 · 15.03.2026 | UP | 200 | 1208 | |
| 15:33:29 · 11.03.2026 | UP | 200 | 1243 | |
| 13:22:52 · 10.03.2026 | UP | 200 | 1408 | |
| 03:19:40 · 10.03.2026 | UP | 200 | 1037 | |
| 03:16:58 · 10.03.2026 | UP | 200 | 1209 | |
| 09:29:12 · 06.03.2026 | UP | 200 | 1010 | |
| 10:49:42 · 05.03.2026 | UP | 200 | 1096 | |
| 04:02:48 · 04.03.2026 | UP | 200 | 958 | |
| 02:28:38 · 03.03.2026 | UP | 200 | 1135 | |
| 02:25:39 · 03.03.2026 | UP | 200 | 1211 | |
| 00:11:33 · 02.03.2026 | UP | 200 | 1058 | |
| 01:58:21 · 01.03.2026 | UP | 200 | 1340 | |
| 14:05:16 · 28.02.2026 | UP | 200 | 1402 | |
| 11:27:48 · 28.02.2026 | UP | 200 | 1098 | |
| 20:55:14 · 27.02.2026 | UP | 200 | 1177 | |
| 01:50:42 · 25.02.2026 | UP | 200 | 858 | |
| 01:06:39 · 25.02.2026 | UP | 200 | 977 | |
| 21:57:11 · 24.02.2026 | UP | 200 | 1519 | |
| 14:53:01 · 24.02.2026 | UP | 200 | 1363 |
07:58:32
15.03.2026
UP HTTP 200 · 987ms
00:52:03
15.03.2026
UP HTTP 200 · 1208ms
15:33:29
11.03.2026
UP HTTP 200 · 1243ms
13:22:52
10.03.2026
UP HTTP 200 · 1408ms
03:19:40
10.03.2026
UP HTTP 200 · 1037ms
03:16:58
10.03.2026
UP HTTP 200 · 1209ms
09:29:12
06.03.2026
UP HTTP 200 · 1010ms
10:49:42
05.03.2026
UP HTTP 200 · 1096ms
04:02:48
04.03.2026
UP HTTP 200 · 958ms
02:28:38
03.03.2026
UP HTTP 200 · 1135ms
02:25:39
03.03.2026
UP HTTP 200 · 1211ms
00:11:33
02.03.2026
UP HTTP 200 · 1058ms
01:58:21
01.03.2026
UP HTTP 200 · 1340ms
14:05:16
28.02.2026
UP HTTP 200 · 1402ms
11:27:48
28.02.2026
UP HTTP 200 · 1098ms
20:55:14
28.02.2026
UP HTTP 200 · 1177ms
01:50:42
25.02.2026
UP HTTP 200 · 858ms
01:06:39
25.02.2026
UP HTTP 200 · 977ms
21:57:11
25.02.2026
UP HTTP 200 · 1519ms
14:53:01
24.02.2026
UP HTTP 200 · 1363ms
Last Detected Downtime
Recently Checked Sites
| Website | Status | HTTP | Response | Uptime | |
|---|---|---|---|---|---|
| UP | 200 | 43 ms | 100% |
||
| UP | 200 | 289 ms | 100% |
||
| UP | 200 | 84 ms | 100% |
||
| UP | 200 | 229 ms | 100% |
||
| UP | 200 | 322 ms | 100% |
||
| UP | 200 | 347 ms | 81.3% |
||
| UP | 200 | 109 ms | 100% |
||
| UP | 200 | 109 ms | 100% |
||
| UP | 200 | 327 ms | 100% |
||
| UP | 200 | 731 ms | 100% |
About This Check
We send an HTTP HEAD request from our Frankfurt, Germany server to vodacom.co.za. A response of HTTP 200–399 within 10 seconds = UP. Any timeout, DNS failure, or error code = DOWN. A rolling history of the last 20 checks is stored and displayed above.
If the site shows UP here but you can't access it, the issue is local — flush your DNS cache (ipconfig /flushdns on Windows / sudo dscacheutil -flushcache on macOS) or try a different network.