Is It Down? emtel.com
UP
Current
200
HTTP Code
4301
Response ms
100%
Uptime (20)
2
Outages
Response Time Last 20 Checks
UP DOWN
Recent Checks (Last 20 Pings)
| Time (America/New_York) | Status | HTTP Code | Response (ms) | |
|---|---|---|---|---|
| 20:53:51 · 12.05.2026 | UP | 200 | 4301 | |
| 03:45:02 · 12.05.2026 | UP | 200 | 4487 | |
| 03:35:05 · 12.05.2026 | UP | 200 | 4458 | |
| 16:45:25 · 11.05.2026 | UP | 200 | 4695 | |
| 16:23:02 · 11.05.2026 | UP | 200 | 4419 | |
| 03:35:44 · 11.05.2026 | UP | 200 | 4809 | |
| 19:06:00 · 09.05.2026 | UP | 200 | 4411 | |
| 13:36:11 · 09.05.2026 | UP | 200 | 5554 | |
| 11:14:55 · 08.05.2026 | UP | 200 | 4906 | |
| 16:46:25 · 07.05.2026 | UP | 200 | 4394 | |
| 06:05:58 · 07.05.2026 | UP | 200 | 4341 | |
| 17:31:16 · 06.05.2026 | UP | 200 | 4161 | |
| 13:35:40 · 05.05.2026 | UP | 200 | 4076 | |
| 04:04:38 · 05.05.2026 | UP | 200 | 4123 | |
| 03:55:42 · 05.05.2026 | UP | 200 | 4212 | |
| 13:32:57 · 04.05.2026 | UP | 200 | 4573 | |
| 05:27:12 · 04.05.2026 | UP | 200 | 4739 | |
| 00:27:47 · 03.05.2026 | UP | 200 | 3799 | |
| 17:09:37 · 02.05.2026 | UP | 200 | 4056 | |
| 13:10:54 · 01.05.2026 | UP | 200 | 4081 |
20:53:51
12.05.2026
UP HTTP 200 · 4301ms
03:45:02
12.05.2026
UP HTTP 200 · 4487ms
03:35:05
12.05.2026
UP HTTP 200 · 4458ms
16:45:25
11.05.2026
UP HTTP 200 · 4695ms
16:23:02
11.05.2026
UP HTTP 200 · 4419ms
03:35:44
11.05.2026
UP HTTP 200 · 4809ms
19:06:00
09.05.2026
UP HTTP 200 · 4411ms
13:36:11
09.05.2026
UP HTTP 200 · 5554ms
11:14:55
08.05.2026
UP HTTP 200 · 4906ms
16:46:25
07.05.2026
UP HTTP 200 · 4394ms
06:05:58
07.05.2026
UP HTTP 200 · 4341ms
17:31:16
06.05.2026
UP HTTP 200 · 4161ms
13:35:40
05.05.2026
UP HTTP 200 · 4076ms
04:04:38
05.05.2026
UP HTTP 200 · 4123ms
03:55:42
05.05.2026
UP HTTP 200 · 4212ms
13:32:57
04.05.2026
UP HTTP 200 · 4573ms
05:27:12
04.05.2026
UP HTTP 200 · 4739ms
00:27:47
03.05.2026
UP HTTP 200 · 3799ms
17:09:37
02.05.2026
UP HTTP 200 · 4056ms
13:10:54
01.05.2026
UP HTTP 200 · 4081ms
Last Detected Downtime
Operation timed out after 10001 milliseconds with 0 bytes received
All Recorded Outages
| Time (America/New_York) | HTTP | Response (ms) | Error | |
|---|---|---|---|---|
| 2026-05-01 00:27:59 | 307 | 10506 | ||
| 2026-05-01 00:26:48 | 307 | 10505 |
00:27:59
01.05.2026
DOWN
HTTP 307 · 10506ms
00:26:48
01.05.2026
DOWN
HTTP 307 · 10505ms
Recently Checked Sites
| Website | Status | HTTP | Response | Uptime | |
|---|---|---|---|---|---|
| DOWN | 6001 ms | 0% |
|||
| DOWN | 42 ms | 0% |
|||
| UP | 200 | 602 ms | 87.5% |
||
| UP | 200 | 60 ms | 100% |
||
| DOWN | 406 | 461 ms | 0% |
||
| UP | 200 | 4301 ms | 100% |
||
| UP | 200 | 46 ms | 100% |
||
| UP | 200 | 145 ms | 100% |
||
| UP | 200 | 332 ms | 15% |
||
| UP | 200 | 85 ms | 100% |
About This Check
We send an HTTP HEAD request from our Frankfurt, Germany server to emtel.com. 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.