Copied!

Is It Down? ebay.com

ebay.com

https://ebay.com · UP · DownDetector

All sites WHOIS

Host: ebay.com Server: Frankfurt, DE Timezone: America/New_York History: 20 / 20 checks Site is UP

Live monitoring · last checked 20:53:47

60

sec until next refresh

UP

Current

200

HTTP Code

556

Response ms

100%

Uptime (20)

9

Outages

Response Time Last 20 Checks

UP DOWN

Recent Checks (Last 20 Pings)

	Time (America/New_York)	Status	HTTP Code	Response (ms)
	20:53:47 · 12.05.2026	UP	200	556
	20:40:11 · 12.05.2026	UP	200	590
	20:20:14 · 12.05.2026	UP	200	499
	20:00:13 · 12.05.2026	UP	200	688
	19:40:12 · 12.05.2026	UP	200	1084
	19:20:12 · 12.05.2026	UP	200	603
	19:00:12 · 12.05.2026	UP	200	540
	18:40:13 · 12.05.2026	UP	200	537
	18:20:14 · 12.05.2026	UP	200	754
	18:00:14 · 12.05.2026	UP	200	791
	17:40:13 · 12.05.2026	UP	200	564
	17:20:14 · 12.05.2026	UP	200	1116
	17:00:14 · 12.05.2026	UP	200	568
	16:40:13 · 12.05.2026	UP	200	539
	16:20:14 · 12.05.2026	UP	200	684
	16:00:14 · 12.05.2026	UP	200	690
	15:40:13 · 12.05.2026	UP	200	589
	15:20:15 · 12.05.2026	UP	200	605
	15:00:17 · 12.05.2026	UP	200	808
	14:40:15 · 12.05.2026	UP	200	671

20:53:47

12.05.2026

UP HTTP 200 · 556ms

20:40:11

12.05.2026

UP HTTP 200 · 590ms

20:20:14

12.05.2026

UP HTTP 200 · 499ms

20:00:13

12.05.2026

UP HTTP 200 · 688ms

19:40:12

12.05.2026

UP HTTP 200 · 1084ms

19:20:12

12.05.2026

UP HTTP 200 · 603ms

19:00:12

12.05.2026

UP HTTP 200 · 540ms

18:40:13

12.05.2026

UP HTTP 200 · 537ms

18:20:14

12.05.2026

UP HTTP 200 · 754ms

18:00:14

12.05.2026

UP HTTP 200 · 791ms

17:40:13

12.05.2026

UP HTTP 200 · 564ms

17:20:14

12.05.2026

UP HTTP 200 · 1116ms

17:00:14

12.05.2026

UP HTTP 200 · 568ms

16:40:13

12.05.2026

UP HTTP 200 · 539ms

16:20:14

12.05.2026

UP HTTP 200 · 684ms

16:00:14

12.05.2026

UP HTTP 200 · 690ms

15:40:13

12.05.2026

UP HTTP 200 · 589ms

15:20:15

12.05.2026

UP HTTP 200 · 605ms

15:00:17

12.05.2026

UP HTTP 200 · 808ms

14:40:15

12.05.2026

UP HTTP 200 · 671ms

Last Detected Downtime

Detected at 2026-04-27 15:40:33 · HTTP 0 · 10002ms

Operation timed out after 10001 milliseconds with 0 bytes received

All Recorded Outages

	Time (America/New_York)	HTTP	Response (ms)	Error
	2026-04-27 15:40:33		10002	Operation timed out after 10001 milliseconds with 0 bytes received
	2026-04-26 20:00:21	301	10199	Operation timed out after 10001 milliseconds with 0 bytes received
	2026-04-26 19:20:31		10002	Operation timed out after 10001 milliseconds with 0 bytes received
	2026-04-26 18:40:30		10002	Operation timed out after 10001 milliseconds with 0 bytes received
	2026-04-26 18:20:31		10002	Operation timed out after 10001 milliseconds with 0 bytes received
	2026-04-26 17:20:22	301	10206	Operation timed out after 10002 milliseconds with 0 bytes received
	2026-04-26 16:20:22	301	10236	Operation timed out after 8003 milliseconds with 0 bytes received
	2026-04-07 04:00:31	301	10248	Resolving timed out after 6000 milliseconds
	2026-03-30 13:20:23	301	10241	Resolving timed out after 6000 milliseconds

15:40:33

27.04.2026

DOWN HTTP · 10002ms

Operation timed out after 10001 milliseconds with 0 bytes received

20:00:21

26.04.2026

DOWN HTTP 301 · 10199ms

Operation timed out after 10001 milliseconds with 0 bytes received

19:20:31

26.04.2026

DOWN HTTP · 10002ms

Operation timed out after 10001 milliseconds with 0 bytes received

18:40:30

26.04.2026

DOWN HTTP · 10002ms

Operation timed out after 10001 milliseconds with 0 bytes received

18:20:31

26.04.2026

DOWN HTTP · 10002ms

Operation timed out after 10001 milliseconds with 0 bytes received

17:20:22

26.04.2026

DOWN HTTP 301 · 10206ms

Operation timed out after 10002 milliseconds with 0 bytes received

16:20:22

26.04.2026

DOWN HTTP 301 · 10236ms

Operation timed out after 8003 milliseconds with 0 bytes received

04:00:31

07.04.2026

DOWN HTTP 301 · 10248ms

Resolving timed out after 6000 milliseconds

13:20:23

30.03.2026

DOWN HTTP 301 · 10241ms

Resolving timed out after 6000 milliseconds

Recently Checked Sites

	Website	Status	HTTP	Response	Uptime
	findipinfo.com	DOWN		6001 ms	0%
	whitelisted.org	DOWN		42 ms	0%
	doska.ru	UP	200	602 ms	87.5%
	reservas.bahamasclinic.es	UP	200	60 ms	100%
	start.cortera.com	DOWN	406	461 ms	0%
	emtel.com	UP	200	4487 ms	100%
	nogueroleprocurador.es	UP	200	46 ms	100%
	myip.is	UP	200	145 ms	100%
	ip-lookup.net	UP	200	332 ms	15%
	fcalculator.com	UP	200	85 ms	100%

6001ms

DOWN HTTP · 0%

whitelisted.org

42ms

DOWN HTTP · 0%

602ms

UP HTTP 200 · 87.5%

reservas.bahamasclinic.es

60ms

UP HTTP 200 · 100%

start.cortera.com

461ms

DOWN HTTP 406 · 0%

4487ms

UP HTTP 200 · 100%

nogueroleprocurador.es

46ms

UP HTTP 200 · 100%

145ms

UP HTTP 200 · 100%

332ms

UP HTTP 200 · 15%

fcalculator.com

85ms

UP HTTP 200 · 100%

About This Check

We send an HTTP HEAD request from our Frankfurt, Germany server to ebay.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.

For community-reported outage data and user comments, check DownDetector ebay.com.