Exploring the Future Potential of AI-Enabled Smartphone Processors
Uptime Magazine Online IT&C de Black Friday 2013.11.18 - 2013.11.24
1. Uptime Monitoring Report
Weekly report no. 47/2013.
Date range analysed: 18 Nov 2013 — 24 Nov 2013 (7 days).
Monitors covered: Sigmanet.ro, Sensodays.ro, ClickShop.ro, F64.ro, eMAG.ro, Flanco.ro,
evoMAG.ro, Domo.ro, MarketOnline.ro, PCGarage.ro, Azerty.ro, MagazinulTau.ro.
Information included: summary, uptime, outages, latency.
Overall availability:
Outage count:
Total downtime:
Average latency:
63.747%
236
2 days 12 hrs 54 mins 18 secs
3428.0833333333 ms
Sigmanet.ro
overall uptime
total downtime
outages
average latency
2
519 ms
99.93% 4 mins 11 secs
Daily Summary
date
uptime (%)
downtime (t)
outages (count)
latency (ms)
100.00
99.71
100.00
100.00
4 mins 11 secs
-
2
-
638
553
495
458
21 Nov 2013
22 Nov 2013
23 Nov 2013
24 Nov 2013
Availability (Uptime)
Outage Timetable
date
21 Nov 2013
22 Nov 2013
23 Nov 2013
24 Nov 2013
hour: 00
01
02
03
04
05
06
07
08
09
10
11
12
13
14
15
16
17
18
19
20
21
22
23
4
Legend: █ no data █ no downtime █ <10 mins down █ 10+ mins down
Uptime Variation (%)
25-Nov-2013
1/39
Monitive.com Monitoring Report #553
2. Outages
start date, time and reason
duration
1. 22 Nov 2013 00:18:27 — 00:19:25
58 secs
Server returned HTTP code 500, confirmed by Istanbul, TR; Chicago, US
2. 22 Nov 2013 00:44:26 — 00:47:39
3 mins 13 secs
Server returned HTTP code 500, confirmed by New York, US; Istanbul, TR
Latency
Daily Averages
date
dns resolve
connect
pretransfer
first byte
download
total
206
229
223
212
139
151
143
123
0
0
0
0
293
172
129
123
0
1
0
0
638
553
495
458
21 Nov 2013
22 Nov 2013
23 Nov 2013
24 Nov 2013
All values are in milliseconds.
TCP State Daily Breakdown
Country Averages
25-Nov-2013
2/39
Monitive.com Monitoring Report #553
3. Fastest & Slowest Countries
Daily latency breakdown for the fastest and the slowest country latency.
Austria (Fastest)
25-Nov-2013
Australia (Slowest)
3/39
Monitive.com Monitoring Report #553
4. Sensodays.ro
overall uptime
total downtime
outages
96.85% 3 hrs 1 min 34 secs
average latency
4
2,182 ms
Daily Summary
date
uptime (%)
downtime (t)
outages (count)
latency (ms)
70.75
99.58
100.00
100.00
2 hrs 55 mins 29 secs
6 mins 5 secs
-
1
3
-
640
640
584
556
21 Nov 2013
22 Nov 2013
23 Nov 2013
24 Nov 2013
Availability (Uptime)
Outage Timetable
date
hour: 00 01
21 Nov 2013
22 Nov 2013
23 Nov 2013
24 Nov 2013
02
03 04 05 06 07 08 09 10 11 12 13 14 15
16
17
18
19
52
60
60
20 21 22 23
3
6
Legend: █ no data █ no downtime █ <10 mins down █ 10+ mins down
Uptime Variation (%)
Outages
start date, time and reason
duration
1. 21 Nov 2013 16:07:57 — 19:03:26
Operation timed out after 30001 milliseconds with 0 bytes received, confirmed by Istanbul, TR;
Hong Kong, HK
2. 22 Nov 2013 02:02:56 — 02:04:25
2 hrs 55 mins 29
secs
1 min 29 secs
Operation timed out after 30000 milliseconds with 0 bytes received, confirmed by Paris, FR;
Istanbul, TR
3. 22 Nov 2013 02:21:30 — 02:23:33
2 mins 3 secs
Server returned HTTP code 500, confirmed by Istanbul, TR; Chicago, US
4. 22 Nov 2013 02:29:55 — 02:32:28
2 mins 33 secs
Operation timed out after 30000 milliseconds with 0 bytes received, confirmed by Paris, FR;
Istanbul, TR
25-Nov-2013
4/39
Monitive.com Monitoring Report #553
5. Latency
Daily Averages
date
dns resolve
connect
pretransfer
first byte
download
total
174
274
296
273
177
161
150
149
0
0
0
0
240
205
138
134
49
0
0
0
640
640
584
556
21 Nov 2013
22 Nov 2013
23 Nov 2013
24 Nov 2013
All values are in milliseconds.
TCP State Daily Breakdown
Country Averages
25-Nov-2013
5/39
Monitive.com Monitoring Report #553
6. Fastest & Slowest Countries
Daily latency breakdown for the fastest and the slowest country latency.
Austria (Fastest)
25-Nov-2013
Chile (Slowest)
6/39
Monitive.com Monitoring Report #553
7. ClickShop.ro
overall uptime
total downtime
outages
average latency
100.00%
-
-
461 ms
Daily Summary
date
uptime (%)
downtime (t)
outages (count)
latency (ms)
100.00
100.00
100.00
100.00
-
-
440
473
469
452
21 Nov 2013
22 Nov 2013
23 Nov 2013
24 Nov 2013
Availability (Uptime)
Outage Timetable
date
hour: 00
01
02
03
04
05
06
07
08
09
10
11
12
13
14
15
16
17
18
19
20
21
22
23
21 Nov 2013
22 Nov 2013
23 Nov 2013
24 Nov 2013
Legend: █ no data █ no downtime █ <10 mins down █ 10+ mins down
Uptime Variation (%)
Outages
start date, time and reason
duration
Latency
Daily Averages
date
21 Nov 2013
22 Nov 2013
23 Nov 2013
24 Nov 2013
dns resolve
connect
pretransfer
first byte
download
total
209
217
226
208
107
119
117
124
0
0
0
0
124
137
126
120
0
0
0
0
440
473
469
452
All values are in milliseconds.
25-Nov-2013
7/39
Monitive.com Monitoring Report #553
8. TCP State Daily Breakdown
Country Averages
Fastest & Slowest Countries
Daily latency breakdown for the fastest and the slowest country latency.
Austria (Fastest)
25-Nov-2013
Australia (Slowest)
8/39
Monitive.com Monitoring Report #553
9. F64.ro
overall uptime
total downtime
outages
average latency
3
3,673 ms
96.93% 2 hrs 56 mins 38 secs
Daily Summary
date
uptime (%)
downtime (t)
outages (count)
latency (ms)
71.39
99.65
100.00
100.00
2 hrs 51 mins 39 secs
4 mins 59 secs
-
2
1
-
2,065
1,747
2,370
2,245
21 Nov 2013
22 Nov 2013
23 Nov 2013
24 Nov 2013
Availability (Uptime)
Outage Timetable
date
hour: 00 01 02 03 04 05 06 07 08 09 10 11 12 13
15 16 17 18 19
20
21
22
23
45
21 Nov 2013
22 Nov 2013
23 Nov 2013
24 Nov 2013
14
60
60
7
5
Legend: █ no data █ no downtime █ <10 mins down █ 10+ mins down
Uptime Variation (%)
Outages
start date, time and reason
duration
1. 21 Nov 2013 20:01:07 — 20:02:26
1 min 19 secs
Operation timed out after 30000 milliseconds with 0 bytes received, confirmed by Vina del
Mar, CL; Moscow, RU
2. 21 Nov 2013 20:16:24 — 23:06:44
2 hrs 50 mins 20
secs
4 mins 59 secs
Server returned HTTP code 500, confirmed by London, UK; Hong Kong, HK
3. 22 Nov 2013 14:20:33 — 14:25:32
Server returned HTTP code 500, confirmed by Budapest, HU; Amsterdam 2, NL
4. 25 Nov 2013 01:27:03 — 01:29:30
2 mins 27 secs
Operation timed out after 30000 milliseconds with 0 bytes received, confirmed by Hong Kong,
HK; Warsaw, PL
25-Nov-2013
9/39
Monitive.com Monitoring Report #553
10. Latency
Daily Averages
date
dns resolve
connect
pretransfer
first byte
download
total
245
113
129
115
218
184
175
169
0
0
0
0
1,552
771
1,436
1,402
50
679
630
559
2,065
1,747
2,370
2,245
21 Nov 2013
22 Nov 2013
23 Nov 2013
24 Nov 2013
All values are in milliseconds.
TCP State Daily Breakdown
Country Averages
25-Nov-2013
10/39
Monitive.com Monitoring Report #553
11. Fastest & Slowest Countries
Daily latency breakdown for the fastest and the slowest country latency.
Romania (Fastest)
25-Nov-2013
Australia (Slowest)
11/39
Monitive.com Monitoring Report #553
12. eMAG.ro
overall uptime
total downtime
outages
average latency
45
18,752 ms
73.64% 1 day 1 hr 18 mins 5 secs
Daily Summary
date
uptime (%)
downtime (t)
outages (count)
latency (ms)
83.83
6.82
96.13
98.37
1 hr 37 mins 2 secs
22 hrs 21 mins 46 secs
55 mins 45 secs
23 mins 32 secs
1
1
28
15
481
870
515
490
21 Nov 2013
22 Nov 2013
23 Nov 2013
24 Nov 2013
Availability (Uptime)
Outage Timetable
date
hour: 00 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23
21 Nov 2013
22 Nov 2013
23 Nov 2013
24 Nov 2013
37 60
60 60 60 60 60 60 60 60 60 60 60 60 60 60 60 60 60 60 60 60 60 60 22
5 17 5
1 5 11
2 1 9
1
2
5
2
4
1 1 0 9
Legend: █ no data █ no downtime █ <10 mins down █ 10+ mins down
Uptime Variation (%)
Outages
start date, time and reason
duration
1. 21 Nov 2013 22:22:58 — 22 Nov 2013 22:21:46
23 hrs 58 mins 48 secs
connect() timed out!, confirmed by Adelaide, AU; Hong Kong, HK
2. 23 Nov 2013 04:32:25 — 04:33:27
1 min 2 secs
Server returned HTTP code 511, confirmed by Budapest, HU; Istanbul, TR
3. 23 Nov 2013 04:34:27 — 04:35:30
1 min 3 secs
Server returned HTTP code 511, confirmed by Istanbul, TR; Budapest, HU
4. 23 Nov 2013 04:56:50 — 04:59:27
2 mins 37 secs
Server returned HTTP code 511, confirmed by Vina del Mar, CL; Budapest, HU
5. 23 Nov 2013 05:04:39 — 05:07:27
2 mins 48 secs
Server returned HTTP code 511, confirmed by Ankara, TR; Vina del Mar, CL
6. 23 Nov 2013 05:12:26 — 05:15:26
3 mins
Server returned HTTP code 511, confirmed by Warsaw, PL; Istanbul, TR
25-Nov-2013
12/39
Monitive.com Monitoring Report #553
13. 7. 23 Nov 2013 05:16:27 — 05:20:35
4 mins 8 secs
Server returned HTTP code 511, confirmed by Warsaw, PL; Istanbul, TR
8. 23 Nov 2013 05:33:27 — 05:35:25
1 min 58 secs
Server returned HTTP code 511, confirmed by Paris, FR; Adelaide, AU
9. 23 Nov 2013 05:37:24 — 05:38:28
1 min 4 secs
Server returned HTTP code 511, confirmed by Paris, FR; Warsaw, PL
10. 23 Nov 2013 05:46:28 — 05:47:27
59 secs
Server returned HTTP code 511, confirmed by Graz, AT; Ankara, TR
11. 23 Nov 2013 05:53:28 — 05:56:43
3 mins 15 secs
Server returned HTTP code 511, confirmed by Warsaw, PL; London, UK
12. 23 Nov 2013 06:01:27 — 06:04:41
3 mins 14 secs
Server returned HTTP code 511, confirmed by Paris, FR; Graz, AT
13. 23 Nov 2013 06:08:27 — 06:10:17
1 min 50 secs
Server returned HTTP code 511, confirmed by Paris, FR; London, UK
14. 23 Nov 2013 08:16:27 — 08:17:25
58 secs
Server returned HTTP code 511, confirmed by Graz, AT; Ankara, TR
15. 23 Nov 2013 09:31:29 — 09:32:27
58 secs
Server returned HTTP code 511, confirmed by Paris, FR; Moscow, RU
16. 23 Nov 2013 09:46:26 — 09:49:26
3 mins
Server returned HTTP code 511, confirmed by Moscow, RU; Warsaw, PL
17. 23 Nov 2013 09:55:42 — 09:56:27
45 secs
Server returned HTTP code 511, confirmed by Vina del Mar, CL; Moscow, RU
18. 23 Nov 2013 10:06:25 — 10:07:44
1 min 19 secs
Server returned HTTP code 511, confirmed by Amsterdam 2, NL; Warsaw, PL
19. 23 Nov 2013 10:14:27 — 10:17:39
3 mins 12 secs
Server returned HTTP code 511, confirmed by Paris, FR; Moscow, RU
20. 23 Nov 2013 10:21:47 — 10:23:28
1 min 41 secs
Server returned HTTP code 511, confirmed by Vina del Mar, CL; Warsaw, PL
21. 23 Nov 2013 10:26:50 — 10:28:28
1 min 38 secs
Server returned HTTP code 511, confirmed by Vina del Mar, CL; Amsterdam 2, NL
22. 23 Nov 2013 10:35:49 — 10:37:32
1 min 43 secs
Server returned HTTP code 511, confirmed by Vina del Mar, CL; Amsterdam 2, NL
23. 23 Nov 2013 10:39:23 — 10:40:49
1 min 26 secs
Server returned HTTP code 511, confirmed by Amsterdam 2, NL; Adelaide, AU
24. 23 Nov 2013 12:43:47 — 12:45:33
1 min 46 secs
Server returned HTTP code 511, confirmed by Ankara, TR; Las Vegas, US
25. 23 Nov 2013 14:20:36 — 14:25:25
4 mins 49 secs
Server returned HTTP code 511, confirmed by Istanbul, TR; Budapest, HU
26. 23 Nov 2013 19:18:37 — 19:20:35
1 min 58 secs
Server returned HTTP code 511, confirmed by Vina del Mar, CL; Graz, AT
27. 23 Nov 2013 23:09:25 — 23:10:47
1 min 22 secs
Server returned HTTP code 511, confirmed by London, UK; Warsaw, PL
28. 23 Nov 2013 23:41:23 — 23:42:31
1 min 8 secs
Server returned HTTP code 511, confirmed by Amsterdam 2, NL; Adelaide, AU
29. 23 Nov 2013 23:54:28 — 23:55:32
1 min 4 secs
Server returned HTTP code 511, confirmed by Warsaw, PL; Adelaide, AU
30. 24 Nov 2013 03:01:33 — 03:02:34
1 min 1 sec
Server returned HTTP code 511, confirmed by Las Vegas, US; Las Vegas, US
31. 24 Nov 2013 03:34:25 — 03:35:26
1 min 1 sec
Server returned HTTP code 511, confirmed by Graz, AT; Vina del Mar, CL
25-Nov-2013
13/39
Monitive.com Monitoring Report #553
14. 32. 24 Nov 2013 04:42:26 — 04:43:24
58 secs
Server returned HTTP code 511, confirmed by Istanbul, TR; London, UK
33. 24 Nov 2013 05:11:26 — 05:13:25
1 min 59 secs
Server returned HTTP code 511, confirmed by London, UK; Istanbul, TR
34. 24 Nov 2013 05:17:26 — 05:18:36
1 min 10 secs
Server returned HTTP code 511, confirmed by Graz, AT; London, UK
35. 24 Nov 2013 05:25:25 — 05:26:26
1 min 1 sec
Server returned HTTP code 511, confirmed by London, UK; Adelaide, AU
36. 24 Nov 2013 05:29:32 — 05:33:25
3 mins 53 secs
Server returned HTTP code 511, confirmed by Adelaide, AU; London, UK
37. 24 Nov 2013 05:58:33 — 05:59:26
53 secs
Server returned HTTP code 511, confirmed by Adelaide, AU; Graz, AT
38. 24 Nov 2013 09:58:25 — 09:59:28
1 min 3 secs
Server returned HTTP code 511, confirmed by Amsterdam 2, NL; London, UK
39. 24 Nov 2013 12:50:37 — 12:51:28
51 secs
Server returned HTTP code 511, confirmed by Istanbul, TR; Graz, AT
40. 24 Nov 2013 13:59:25 — 14:00:19
54 secs
Server returned HTTP code 511, confirmed by Amsterdam 2, NL; Warsaw, PL
41. 24 Nov 2013 15:31:27 — 15:33:26
1 min 59 secs
Server returned HTTP code 511, confirmed by Paris, FR; Budapest, HU
42. 24 Nov 2013 15:38:26 — 15:39:26
1 min
Server returned HTTP code 511, confirmed by Paris, FR; Budapest, HU
43. 24 Nov 2013 15:41:35 — 15:44:25
2 mins 50 secs
Server returned HTTP code 511, confirmed by Vina del Mar, CL; Budapest, HU
44. 24 Nov 2013 15:53:28 — 15:56:27
2 mins 59 secs
Server returned HTTP code 511, confirmed by Paris, FR; Budapest, HU
Latency
Daily Averages
date
dns resolve
connect
pretransfer
first byte
download
total
178
338
200
193
133
362
146
135
0
0
0
0
169
170
168
162
1
0
1
0
481
870
515
490
21 Nov 2013
22 Nov 2013
23 Nov 2013
24 Nov 2013
All values are in milliseconds.
TCP State Daily Breakdown
25-Nov-2013
14/39
Monitive.com Monitoring Report #553
15. Country Averages
Fastest & Slowest Countries
Daily latency breakdown for the fastest and the slowest country latency.
Romania (Fastest)
25-Nov-2013
Chile (Slowest)
15/39
Monitive.com Monitoring Report #553
16. Flanco.ro
overall uptime
total downtime
outages
average latency
14
457 ms
99.38% 35 mins 58 secs
Daily Summary
date
uptime (%)
downtime (t)
outages (count)
latency (ms)
100.00
100.00
100.00
97.50
35 mins 58 secs
14
511
465
439
452
21 Nov 2013
22 Nov 2013
23 Nov 2013
24 Nov 2013
Availability (Uptime)
Outage Timetable
date
hour: 00
01
02
03
04
05
06
07
08
09
10
11
13
14
15
16
17
18
19
20
21
22
23
7
21 Nov 2013
22 Nov 2013
23 Nov 2013
24 Nov 2013
12
29
Legend: █ no data █ no downtime █ <10 mins down █ 10+ mins down
Uptime Variation (%)
Outages
start date, time and reason
duration
1. 24 Nov 2013 22:12:34 — 22:13:56
1 min 22 secs
Server returned HTTP code 503, confirmed by Hong Kong, HK; Ankara, TR
2. 24 Nov 2013 22:22:54 — 22:26:01
3 mins 7 secs
connect() timed out!, confirmed by Budapest, HU; Hong Kong, HK
3. 24 Nov 2013 22:33:26 — 22:34:27
1 min 1 sec
Server returned HTTP code 503, confirmed by Graz, AT; Budapest, HU
4. 24 Nov 2013 22:41:55 — 22:42:46
51 secs
Server returned HTTP code 503, confirmed by Ankara, TR; Graz, AT
5. 24 Nov 2013 22:51:28 — 22:52:24
56 secs
Server returned HTTP code 503, confirmed by Istanbul, TR; Graz, AT
6. 24 Nov 2013 23:00:35 — 23:01:26
51 secs
Server returned HTTP code 503, confirmed by London, UK; Budapest, HU
25-Nov-2013
16/39
Monitive.com Monitoring Report #553
17. 7. 24 Nov 2013 23:02:25 — 23:07:56
5 mins 31 secs
Server returned HTTP code 503, confirmed by Budapest, HU; Hong Kong, HK
8. 24 Nov 2013 23:10:53 — 23:15:25
4 mins 32 secs
Server returned HTTP code 503, confirmed by Hong Kong, HK; Ankara, TR
9. 24 Nov 2013 23:24:25 — 23:29:25
5 mins
Server returned HTTP code 503, confirmed by Budapest, HU; Ankara, TR
10. 24 Nov 2013 23:32:28 — 23:36:26
3 mins 58 secs
Server returned HTTP code 503, confirmed by Las Vegas, US; Paris, FR
11. 24 Nov 2013 23:37:23 — 23:38:29
1 min 6 secs
Server returned HTTP code 503, confirmed by Paris, FR; Las Vegas, US
12. 24 Nov 2013 23:40:47 — 23:45:25
4 mins 38 secs
Server returned HTTP code 503, confirmed by Hong Kong, HK; Moscow, RU
13. 24 Nov 2013 23:49:55 — 23:52:25
2 mins 30 secs
Server returned HTTP code 503, confirmed by Vina del Mar, CL; London, UK
14. 24 Nov 2013 23:59:25 — 25 Nov 2013 00:00:35
1 min 10 secs
Server returned HTTP code 503, confirmed by Moscow, RU; Ankara, TR
15. 25 Nov 2013 00:01:25 — 00:15:24
13 mins 59 secs
Server returned HTTP code 503, confirmed by Budapest, HU; Vina del Mar, CL
16. 25 Nov 2013 00:18:26 — 00:19:29
1 min 3 secs
Server returned HTTP code 503, confirmed by Graz, AT; Vina del Mar, CL
17. 25 Nov 2013 00:22:44 — 00:33:24
10 mins 40 secs
Server returned HTTP code 503, confirmed by Ankara, TR; London, UK
18. 25 Nov 2013 00:35:50 — 00:40:16
4 mins 26 secs
Server returned HTTP code 503, confirmed by Vina del Mar, CL; Budapest, HU
19. 25 Nov 2013 00:43:39 — 00:49:15
5 mins 36 secs
Server returned HTTP code 503, confirmed by Ankara, TR; Graz, AT
20. 25 Nov 2013 00:50:35 — 01:10:34
19 mins 59 secs
Server returned HTTP code 503, confirmed by Warsaw, PL; Graz, AT
21. 25 Nov 2013 01:11:28 — 01:18:26
6 mins 58 secs
Server returned HTTP code 503, confirmed by Paris, FR; Istanbul, TR
22. 25 Nov 2013 01:20:35 — 01:35:30
14 mins 55 secs
Server returned HTTP code 503, confirmed by Istanbul, TR; Amsterdam 2, NL
23. 25 Nov 2013 01:36:26 — 10:16:28
8 hrs 40 mins 2 secs
Server returned HTTP code 503, confirmed by Warsaw, PL; Budapest, HU
Latency
Daily Averages
date
21 Nov 2013
22 Nov 2013
23 Nov 2013
24 Nov 2013
dns resolve
connect
pretransfer
first byte
download
total
224
192
176
203
148
136
134
128
0
0
0
0
139
137
129
121
0
0
0
0
511
465
439
452
All values are in milliseconds.
25-Nov-2013
17/39
Monitive.com Monitoring Report #553
18. TCP State Daily Breakdown
Country Averages
Fastest & Slowest Countries
Daily latency breakdown for the fastest and the slowest country latency.
Austria (Fastest)
25-Nov-2013
Hong Kong (Slowest)
18/39
Monitive.com Monitoring Report #553
19. evoMAG.ro
overall uptime
total downtime
outages
average latency
100.00%
-
-
953 ms
Daily Summary
date
uptime (%)
downtime (t)
outages (count)
latency (ms)
100.00
100.00
100.00
100.00
-
-
703
1,007
981
980
21 Nov 2013
22 Nov 2013
23 Nov 2013
24 Nov 2013
Availability (Uptime)
Outage Timetable
date
hour: 00
01
02
03
04
05
06
07
08
09
10
11
12
13
14
15
16
17
18
19
20
21
22
23
21 Nov 2013
22 Nov 2013
23 Nov 2013
24 Nov 2013
Legend: █ no data █ no downtime █ <10 mins down █ 10+ mins down
Uptime Variation (%)
Outages
start date, time and reason
duration
1. 25 Nov 2013 00:03:27 — 00:22:38
19 mins 11 secs
Server returned HTTP code 404, confirmed by London, UK; Warsaw, PL
Latency
Daily Averages
date
21 Nov 2013
22 Nov 2013
23 Nov 2013
24 Nov 2013
dns resolve
connect
pretransfer
first byte
download
total
226
174
170
157
143
157
137
142
0
0
0
0
186
141
133
144
148
535
541
537
703
1,007
981
980
All values are in milliseconds.
25-Nov-2013
19/39
Monitive.com Monitoring Report #553
20. TCP State Daily Breakdown
Country Averages
Fastest & Slowest Countries
Daily latency breakdown for the fastest and the slowest country latency.
Austria (Fastest)
25-Nov-2013
Chile (Slowest)
20/39
Monitive.com Monitoring Report #553
21. Domo.ro
overall uptime
total downtime
outages
70
73.65% 1 day 1 hr 17 mins 52 secs
average latency
10,783 ms
Daily Summary
date
uptime (%)
downtime (t)
outages (count)
latency (ms)
69.94
20.95
86.17
100.00
3 hrs 23 secs
18 hrs 58 mins 23 secs
3 hrs 19 mins 6 secs
-
8
38
24
-
1,714
9,981
5,121
1,210
21 Nov 2013
22 Nov 2013
23 Nov 2013
24 Nov 2013
Availability (Uptime)
Outage Timetable
date
hour: 00 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23
21 Nov 2013
22 Nov 2013
23 Nov 2013
24 Nov 2013
16 45 54 37 29
1 40 10 6 14 37 60 60 60 49 60 60 48 60 60 60 60 60 55 58 60 60 53 46
3
2 13 29 17 17 55 60 1
3
Legend: █ no data █ no downtime █ <10 mins down █ 10+ mins down
Uptime Variation (%)
Outages
start date, time and reason
duration
1. 21 Nov 2013 19:15:57 — 19:17:54
1 min 57 secs
connect() timed out!, confirmed by Las Vegas, US; Hong Kong, HK
2. 21 Nov 2013 19:29:56 — 19:37:25
7 mins 29 secs
connect() timed out!, confirmed by Las Vegas, US; Adelaide, AU
3. 21 Nov 2013 19:47:57 — 19:54:29
6 mins 32 secs
connect() timed out!, confirmed by Las Vegas, US; Moscow, RU
4. 21 Nov 2013 20:08:52 — 20:28:32
19 mins 40 secs
couldn't connect to host, confirmed by Paris, FR; Istanbul, TR
5. 21 Nov 2013 20:35:01 — 21:06:28
31 mins 27 secs
Operation timed out after 30000 milliseconds with 0 bytes received, confirmed by Hong Kong,
HK; New York, US
25-Nov-2013
21/39
Monitive.com Monitoring Report #553
22. 6. 21 Nov 2013 21:08:56 — 21:36:30
27 mins 34 secs
Operation timed out after 30000 milliseconds with 0 bytes received, confirmed by Paris, FR;
Los Angeles, US
7. 21 Nov 2013 21:39:54 — 22:36:34
56 mins 40 secs
Server returned HTTP code 500, confirmed by Ankara, TR; Moscow, RU
8. 21 Nov 2013 23:30:56 — 22 Nov 2013 00:01:28
30 mins 32 secs
couldn't connect to host, confirmed by Warsaw, PL; Vina del Mar, CL
9. 22 Nov 2013 01:01:07 — 01:24:36
23 mins 29 secs
couldn't connect to host, confirmed by Hong Kong, HK; Ankara, TR
10. 22 Nov 2013 01:36:55 — 01:53:32
16 mins 37 secs
Operation timed out after 30001 milliseconds with 0 bytes received, confirmed by
Amsterdam 2, NL; Las Vegas, US
11. 22 Nov 2013 02:22:55 — 02:25:27
2 mins 32 secs
connect() timed out!, confirmed by Moscow, RU; London, UK
12. 22 Nov 2013 02:31:56 — 02:33:28
1 min 32 secs
connect() timed out!, confirmed by Budapest, HU; Chicago, US
13. 22 Nov 2013 02:38:54 — 02:44:30
5 mins 36 secs
connect() timed out!, confirmed by Los Angeles, US; Las Vegas, US
14. 22 Nov 2013 03:12:46 — 03:13:28
42 secs
couldn't connect to host, confirmed by Paris, FR; London, UK
15. 22 Nov 2013 03:25:47 — 03:27:55
2 mins 8 secs
couldn't connect to host, confirmed by London, UK; Chicago, US
16. 22 Nov 2013 03:49:52 — 03:51:47
1 min 55 secs
couldn't connect to host, confirmed by Paris, FR; Los Angeles, US
17. 22 Nov 2013 03:58:59 — 04:01:57
2 mins 58 secs
connect() timed out!, confirmed by Las Vegas, US; Adelaide, AU
18. 22 Nov 2013 04:03:55 — 04:05:53
1 min 58 secs
connect() timed out!, confirmed by Amsterdam 2, NL; Las Vegas, US
19. 22 Nov 2013 04:06:48 — 04:09:35
2 mins 47 secs
couldn't connect to host, confirmed by Warsaw, PL; Graz, AT
20. 22 Nov 2013 04:32:57 — 04:34:57
2 mins
couldn't connect to host, confirmed by Vina del Mar, CL; Las Vegas, US
21. 22 Nov 2013 04:41:04 — 04:43:30
2 mins 26 secs
connect() timed out!, confirmed by Los Angeles, US; Graz, AT
22. 22 Nov 2013 04:55:53 — 04:58:46
2 mins 53 secs
couldn't connect to host, confirmed by Warsaw, PL; New York, US
23. 22 Nov 2013 05:00:57 — 05:02:32
1 min 35 secs
couldn't connect to host, confirmed by Warsaw, PL; Budapest, HU
24. 22 Nov 2013 05:10:55 — 05:12:56
2 mins 1 sec
couldn't connect to host, confirmed by Graz, AT; Moscow, RU
25. 22 Nov 2013 05:15:47 — 05:17:55
2 mins 8 secs
couldn't connect to host, confirmed by London, UK; Warsaw, PL
26. 22 Nov 2013 05:25:46 — 05:28:33
2 mins 47 secs
couldn't connect to host, confirmed by Graz, AT; Warsaw, PL
27. 22 Nov 2013 05:31:04 — 09:00:24
3 hrs 29 mins 20
secs
1 min 46 secs
connect() timed out!, confirmed by New York, US; Adelaide, AU
28. 22 Nov 2013 09:04:08 — 09:05:54
couldn't connect to host, confirmed by Vina del Mar, CL; Hong Kong, HK
29. 22 Nov 2013 09:08:58 — 09:15:54
6 mins 56 secs
Operation timed out after 30000 milliseconds with 0 bytes received, confirmed by Moscow,
RU; Las Vegas, US
25-Nov-2013
22/39
Monitive.com Monitoring Report #553
23. 30. 22 Nov 2013 09:17:18 — 09:19:32
2 mins 14 secs
Operation timed out after 30000 milliseconds with 0 bytes received, confirmed by Adelaide,
AU; Istanbul, TR
31. 22 Nov 2013 09:21:55 — 12:01:04
Recv failure: Connection reset by peer, confirmed by Budapest, HU; Hong Kong, HK
32. 22 Nov 2013 12:02:58 — 12:11:30
2 hrs 39 mins 9
secs
8 mins 32 secs
connect() timed out!, confirmed by Istanbul, TR; Warsaw, PL
33. 22 Nov 2013 12:21:31 — 18:33:53
6 hrs 12 mins 22
secs
11 mins 4 secs
Server returned HTTP code 500, confirmed by Istanbul, TR; Hong Kong, HK
34. 22 Nov 2013 18:35:55 — 18:46:59
Operation timed out after 30000 milliseconds with 0 bytes received, confirmed by Budapest,
HU; Ankara, TR
35. 22 Nov 2013 18:47:55 — 18:56:55
9 mins
Operation timed out after 30000 milliseconds with 0 bytes received, confirmed by Moscow,
RU; Hong Kong, HK
36. 22 Nov 2013 18:58:56 — 19:33:52
34 mins 56 secs
Operation timed out after 30001 milliseconds with 0 bytes received, confirmed by London,
UK; Vina del Mar, CL
37. 22 Nov 2013 19:36:02 — 22:30:51
Operation timed out after 30001 milliseconds with 0 bytes received, confirmed by
Amsterdam 2, NL; Adelaide, AU
38. 22 Nov 2013 22:32:58 — 22:36:46
2 hrs 54 mins 49
secs
3 mins 48 secs
Operation timed out after 30000 milliseconds with 0 bytes received, confirmed by Las Vegas,
US; Hong Kong, HK
39. 22 Nov 2013 22:38:59 — 22:46:49
7 mins 50 secs
Operation timed out after 30001 milliseconds with 0 bytes received, confirmed by
Amsterdam 2, NL; Istanbul, TR
40. 22 Nov 2013 22:48:04 — 22:58:43
10 mins 39 secs
Operation timed out after 30000 milliseconds with 0 bytes received, confirmed by Vina del
Mar, CL; London, UK
41. 22 Nov 2013 22:59:58 — 23:14:35
14 mins 37 secs
Operation timed out after 30000 milliseconds with 0 bytes received, confirmed by Las Vegas,
US; Moscow, RU
42. 22 Nov 2013 23:17:57 — 23:32:41
14 mins 44 secs
Operation timed out after 30000 milliseconds with 0 bytes received, confirmed by Paris, FR;
London, UK
43. 22 Nov 2013 23:36:05 — 23:44:35
8 mins 30 secs
Operation timed out after 30000 milliseconds with 0 bytes received, confirmed by Las Vegas,
US; Vina del Mar, CL
44. 22 Nov 2013 23:49:55 — 23:57:34
7 mins 39 secs
Operation timed out after 30001 milliseconds with 0 bytes received, confirmed by Moscow,
RU; Ankara, TR
45. 22 Nov 2013 23:59:04 — 23 Nov 2013 00:03:00
3 mins 56 secs
Operation timed out after 30001 milliseconds with 0 bytes received, confirmed by Paris, FR;
Vina del Mar, CL
46. 23 Nov 2013 08:58:00 — 09:00:29
2 mins 29 secs
Operation timed out after 30001 milliseconds with 0 bytes received, confirmed by Adelaide,
AU; Paris, FR
47. 23 Nov 2013 09:31:04 — 09:35:54
4 mins 50 secs
Operation timed out after 30001 milliseconds with 0 bytes received, confirmed by Moscow,
RU; Paris, FR
48. 23 Nov 2013 09:37:56 — 09:40:54
2 mins 58 secs
Operation timed out after 30000 milliseconds with 0 bytes received, confirmed by Las Vegas,
US; Adelaide, AU
25-Nov-2013
23/39
Monitive.com Monitoring Report #553
24. 49. 23 Nov 2013 09:44:03 — 09:46:46
2 mins 43 secs
Operation timed out after 30001 milliseconds with 0 bytes received, confirmed by Istanbul,
TR; London, UK
50. 23 Nov 2013 09:52:55 — 09:54:42
1 min 47 secs
Operation timed out after 30001 milliseconds with 0 bytes received, confirmed by Moscow,
RU; Hong Kong, HK
51. 23 Nov 2013 10:19:17 — 10:26:54
7 mins 37 secs
Operation timed out after 30001 milliseconds with 0 bytes received, confirmed by Graz, AT;
Paris, FR
52. 23 Nov 2013 10:36:59 — 10:51:54
14 mins 55 secs
Operation timed out after 30000 milliseconds with 0 bytes received, confirmed by Adelaide,
AU; Moscow, RU
53. 23 Nov 2013 10:53:59 — 11:00:36
6 mins 37 secs
Operation timed out after 30001 milliseconds with 0 bytes received, confirmed by
Amsterdam 2, NL; Las Vegas, US
54. 23 Nov 2013 11:06:17 — 11:09:41
3 mins 24 secs
Operation timed out after 30001 milliseconds with 0 bytes received, confirmed by Moscow,
RU; Adelaide, AU
55. 23 Nov 2013 11:16:03 — 11:18:56
2 mins 53 secs
Operation timed out after 30000 milliseconds with 0 bytes received, confirmed by
Amsterdam 2, NL; Budapest, HU
56. 23 Nov 2013 11:23:09 — 11:33:41
10 mins 32 secs
Operation timed out after 30001 milliseconds with 0 bytes received, confirmed by Hong Kong,
HK; Warsaw, PL
57. 23 Nov 2013 11:59:56 — 12:00:46
50 secs
Operation timed out after 30001 milliseconds with 0 bytes received, confirmed by Warsaw,
PL; Moscow, RU
58. 23 Nov 2013 12:12:58 — 12:15:43
2 mins 45 secs
Operation timed out after 30000 milliseconds with 0 bytes received, confirmed by Istanbul,
TR; Moscow, RU
59. 23 Nov 2013 12:20:01 — 12:22:30
2 mins 29 secs
Operation timed out after 30000 milliseconds with 0 bytes received, confirmed by Adelaide,
AU; Istanbul, TR
60. 23 Nov 2013 12:30:46 — 12:31:49
1 min 3 secs
Empty reply from server, confirmed by Adelaide, AU; Warsaw, PL
61. 23 Nov 2013 12:35:08 — 12:36:59
1 min 51 secs
Operation timed out after 30000 milliseconds with 0 bytes received, confirmed by Hong Kong,
HK; Las Vegas, US
62. 23 Nov 2013 12:41:58 — 12:45:05
3 mins 7 secs
Operation timed out after 30000 milliseconds with 0 bytes received, confirmed by Adelaide,
AU; Hong Kong, HK
63. 23 Nov 2013 12:48:56 — 12:50:33
1 min 37 secs
Operation timed out after 30000 milliseconds with 0 bytes received, confirmed by Istanbul,
TR; Las Vegas, US
64. 23 Nov 2013 12:54:16 — 12:55:40
1 min 24 secs
Operation timed out after 30000 milliseconds with 0 bytes received, confirmed by Hong Kong,
HK; Vina del Mar, CL
65. 23 Nov 2013 12:58:09 — 13:02:03
3 mins 54 secs
Operation timed out after 30001 milliseconds with 0 bytes received, confirmed by Adelaide,
AU; Ankara, TR
66. 23 Nov 2013 13:04:57 — 13:07:43
2 mins 46 secs
Operation timed out after 30001 milliseconds with 0 bytes received, confirmed by Moscow,
RU; Vina del Mar, CL
67. 23 Nov 2013 13:10:03 — 15:00:34
Operation timed out after 30000 milliseconds with 0 bytes received, confirmed by Vina del
Mar, CL; Budapest, HU
25-Nov-2013
24/39
1 hr 50 mins 31
secs
Monitive.com Monitoring Report #553
25. 68. 23 Nov 2013 17:03:39 — 17:06:43
3 mins 4 secs
Server returned HTTP code 502, confirmed by Graz, AT; Vina del Mar, CL
Latency
Daily Averages
date
dns resolve
connect
pretransfer
first byte
download
total
290
144
154
147
970
1,539
146
136
0
0
0
0
387
3,718
2,205
286
67
4,580
2,616
641
1,714
9,981
5,121
1,210
21 Nov 2013
22 Nov 2013
23 Nov 2013
24 Nov 2013
All values are in milliseconds.
TCP State Daily Breakdown
Country Averages
25-Nov-2013
25/39
Monitive.com Monitoring Report #553
26. Fastest & Slowest Countries
Daily latency breakdown for the fastest and the slowest country latency.
Romania (Fastest)
25-Nov-2013
Australia (Slowest)
26/39
Monitive.com Monitoring Report #553
27. MarketOnline.ro
overall uptime
total downtime
outages
14
99.39% 35 mins 22 secs
average latency
707 ms
Daily Summary
date
uptime (%)
downtime (t)
outages (count)
latency (ms)
97.83
98.45
100.00
100.00
13 mins 2 secs
22 mins 20 secs
-
5
9
-
1,467
850
475
432
21 Nov 2013
22 Nov 2013
23 Nov 2013
24 Nov 2013
Availability (Uptime)
Outage Timetable
date
hour:
21 Nov 2013
22 Nov 2013
23 Nov 2013
24 Nov 2013
00
01 02 03 04 05 06 07 08
09
10
11
12 13 14 15 16 17 18 19 20 21 22
23
13
17
2
2
2
Legend: █ no data █ no downtime █ <10 mins down █ 10+ mins down
Uptime Variation (%)
Outages
start date, time and reason
duration
1. 21 Nov 2013 23:12:55 — 23:14:55
2 mins
Operation timed out after 30000 milliseconds with 0 bytes received, confirmed by Istanbul, TR;
Budapest, HU
2. 21 Nov 2013 23:16:58 — 23:18:25
1 min 27 secs
Operation timed out after 30000 milliseconds with 0 bytes received, confirmed by Chicago, US; Vina
del Mar, CL
3. 21 Nov 2013 23:21:56 — 23:27:28
5 mins 32 secs
Operation timed out after 30000 milliseconds with 0 bytes received, confirmed by Paris, FR; Ankara,
TR
4. 21 Nov 2013 23:51:27 — 23:53:29
2 mins 2 secs
Recv failure: Connection reset by peer, confirmed by Warsaw, PL; London, UK
25-Nov-2013
27/39
Monitive.com Monitoring Report #553
28. 5. 21 Nov 2013 23:57:59 — 22 Nov 2013 00:00:31
2 mins 32 secs
Operation timed out after 30000 milliseconds with 0 bytes received, confirmed by Adelaide, AU; Los
Angeles, US
6. 22 Nov 2013 00:01:55 — 00:04:53
2 mins 58 secs
Operation timed out after 30001 milliseconds with 0 bytes received, confirmed by Amsterdam 2, NL;
Istanbul, TR
7. 22 Nov 2013 00:09:53 — 00:12:29
2 mins 36 secs
Operation timed out after 30001 milliseconds with 0 bytes received, confirmed by Moscow, RU; Las
Vegas, US
8. 22 Nov 2013 00:14:54 — 00:20:55
6 mins 1 sec
Operation timed out after 30001 milliseconds with 0 bytes received, confirmed by London, UK;
Ankara, TR
9. 22 Nov 2013 00:22:25 — 00:23:53
1 min 28 secs
couldn't connect to host, confirmed by Paris, FR; Moscow, RU
10. 22 Nov 2013 00:31:56 — 00:34:54
2 mins 58 secs
Operation timed out after 30000 milliseconds with 0 bytes received, confirmed by Las Vegas, US;
Los Angeles, US
11. 22 Nov 2013 09:43:39 — 09:45:26
1 min 47 secs
Server returned HTTP code 504, confirmed by Ankara, TR; Budapest, HU
12. 22 Nov 2013 10:27:26 — 10:29:25
1 min 59 secs
Server returned HTTP code 504, confirmed by Amsterdam 2, NL; Moscow, RU
13. 22 Nov 2013 11:29:26 — 11:31:28
2 mins 2 secs
Server returned HTTP code 504, confirmed by Warsaw, PL; Budapest, HU
Latency
Daily Averages
date
dns resolve
connect
pretransfer
first byte
download
total
218
158
162
141
150
167
153
152
0
0
0
0
1,099
525
160
139
0
0
0
0
1,467
850
475
432
21 Nov 2013
22 Nov 2013
23 Nov 2013
24 Nov 2013
All values are in milliseconds.
TCP State Daily Breakdown
25-Nov-2013
28/39
Monitive.com Monitoring Report #553
29. Country Averages
Fastest & Slowest Countries
Daily latency breakdown for the fastest and the slowest country latency.
Austria (Fastest)
25-Nov-2013
Chile (Slowest)
29/39
Monitive.com Monitoring Report #553
30. PCGarage.ro
overall uptime
total downtime
outages
58
97.94% 1 hr 58 mins 41 secs
average latency
548 ms
Daily Summary
date
uptime (%)
downtime (t)
outages (count)
latency (ms)
96.02
98.35
97.27
97.79
23 mins 53 secs
23 mins 46 secs
39 mins 16 secs
31 mins 46 secs
7
12
21
18
869
528
494
491
21 Nov 2013
22 Nov 2013
23 Nov 2013
24 Nov 2013
Availability (Uptime)
Outage Timetable
date
hour: 00
21 Nov 2013
22 Nov 2013
23 Nov 2013
24 Nov 2013
01
03
04
05
06
07
08
09
3
3
3
3
3
10
4
2
2
1
2
4
4
2
11
12
13
14
15
3
16
17
4
2
02
18
2
3
2
3
6
1
1
2
20
15
2
2
19
2
2
1
2
22
23
1
1
5
3
5
21
2
2
2
4
1
6
2
Legend: █ no data █ no downtime █ <10 mins down █ 10+ mins down
Uptime Variation (%)
Outages
start date, time and reason
1.
duration
21 Nov 2013 16:09:53 — 16:11:33
1 min 40 secs
connect() timed out!, confirmed by Istanbul, TR; Budapest, HU
2.
21 Nov 2013 16:17:55 — 16:20:18
2 mins 23 secs
connect() timed out!, confirmed by Istanbul, TR; Budapest, HU
3.
21 Nov 2013 17:02:54 — 17:04:32
1 min 38 secs
connect() timed out!, confirmed by Budapest, HU; Istanbul, TR
4.
21 Nov 2013 19:01:31 — 19:16:27
14 mins 56 secs
Server returned HTTP code 503, confirmed by Adelaide, AU; Los Angeles, US
5.
21 Nov 2013 20:46:54 — 20:48:26
1 min 32 secs
connect() timed out!, confirmed by Budapest, HU; Istanbul, TR
6.
21 Nov 2013 22:09:53 — 22:10:57
1 min 4 secs
connect() timed out!, confirmed by Istanbul, TR; Budapest, HU
25-Nov-2013
30/39
Monitive.com Monitoring Report #553
31. 7.
21 Nov 2013 23:19:54 — 23:20:34
40 secs
connect() timed out!, confirmed by Budapest, HU; Istanbul, TR
8.
22 Nov 2013 01:56:54 — 01:58:33
1 min 39 secs
connect() timed out!, confirmed by Budapest, HU; Istanbul, TR
9.
22 Nov 2013 02:54:55 — 02:57:33
2 mins 38 secs
connect() timed out!, confirmed by Istanbul, TR; Budapest, HU
10. 22 Nov 2013 10:42:55 — 10:45:25
2 mins 30 secs
connect() timed out!, confirmed by Budapest, HU; Istanbul, TR
11. 22 Nov 2013 11:08:03 — 11:09:26
1 min 23 secs
connect() timed out!, confirmed by Istanbul, TR; Budapest, HU
12. 22 Nov 2013 11:41:54 — 11:43:39
1 min 45 secs
connect() timed out!, confirmed by Istanbul, TR; Budapest, HU
13. 22 Nov 2013 16:21:04 — 16:23:26
2 mins 22 secs
connect() timed out!, confirmed by Budapest, HU; Istanbul, TR
14. 22 Nov 2013 19:41:04 — 19:42:37
1 min 33 secs
connect() timed out!, confirmed by Budapest, HU; Istanbul, TR
15. 22 Nov 2013 19:55:59 — 19:57:27
1 min 28 secs
connect() timed out!, confirmed by Istanbul, TR; Budapest, HU
16. 22 Nov 2013 21:09:53 — 21:13:25
3 mins 32 secs
connect() timed out!, confirmed by Budapest, HU; Istanbul, TR
17. 22 Nov 2013 21:48:56 — 21:50:34
1 min 38 secs
connect() timed out!, confirmed by Istanbul, TR; Budapest, HU
18. 22 Nov 2013 22:29:58 — 22:31:32
1 min 34 secs
connect() timed out!, confirmed by Istanbul, TR; Budapest, HU
19. 22 Nov 2013 23:27:57 — 23:29:41
1 min 44 secs
connect() timed out!, confirmed by Istanbul, TR; Budapest, HU
20. 23 Nov 2013 00:37:53 — 00:41:01
3 mins 8 secs
connect() timed out!, confirmed by Budapest, HU; Istanbul, TR
21. 23 Nov 2013 04:31:54 — 04:33:24
1 min 30 secs
connect() timed out!, confirmed by Budapest, HU; Istanbul, TR
22. 23 Nov 2013 04:36:57 — 04:38:27
1 min 30 secs
connect() timed out!, confirmed by Istanbul, TR; Budapest, HU
23. 23 Nov 2013 05:03:55 — 05:05:26
1 min 31 secs
connect() timed out!, confirmed by Istanbul, TR; Budapest, HU
24. 23 Nov 2013 05:07:56 — 05:09:26
1 min 30 secs
connect() timed out!, confirmed by Budapest, HU; Istanbul, TR
25. 23 Nov 2013 05:21:04 — 05:22:26
1 min 22 secs
connect() timed out!, confirmed by Budapest, HU; Istanbul, TR
26. 23 Nov 2013 06:41:54 — 06:43:27
1 min 33 secs
connect() timed out!, confirmed by Budapest, HU; Istanbul, TR
27. 23 Nov 2013 07:02:54 — 07:04:36
1 min 42 secs
connect() timed out!, confirmed by Budapest, HU; Istanbul, TR
28. 23 Nov 2013 07:51:55 — 07:54:35
2 mins 40 secs
connect() timed out!, confirmed by Budapest, HU; Istanbul, TR
29. 23 Nov 2013 08:54:58 — 08:58:30
3 mins 32 secs
connect() timed out!, confirmed by Istanbul, TR; Budapest, HU
30. 23 Nov 2013 10:53:55 — 10:55:28
1 min 33 secs
connect() timed out!, confirmed by Budapest, HU; Istanbul, TR
31. 23 Nov 2013 15:18:55 — 15:20:19
1 min 24 secs
connect() timed out!, confirmed by Budapest, HU; Istanbul, TR
25-Nov-2013
31/39
Monitive.com Monitoring Report #553
32. 32. 23 Nov 2013 15:27:55 — 15:29:34
1 min 39 secs
connect() timed out!, confirmed by Budapest, HU; Istanbul, TR
33. 23 Nov 2013 16:36:57 — 16:38:26
1 min 29 secs
connect() timed out!, confirmed by Istanbul, TR; Budapest, HU
34. 23 Nov 2013 18:53:56 — 18:58:26
4 mins 30 secs
connect() timed out!, confirmed by Budapest, HU; Istanbul, TR
35. 23 Nov 2013 19:15:56 — 19:17:27
1 min 31 secs
connect() timed out!, confirmed by Istanbul, TR; Budapest, HU
36. 23 Nov 2013 19:59:55 — 20:00:49
54 secs
connect() timed out!, confirmed by Budapest, HU; Istanbul, TR
37. 23 Nov 2013 21:57:54 — 21:59:26
1 min 32 secs
connect() timed out!, confirmed by Budapest, HU; Istanbul, TR
38. 23 Nov 2013 22:06:57 — 22:08:42
1 min 45 secs
connect() timed out!, confirmed by Istanbul, TR; Budapest, HU
39. 23 Nov 2013 22:52:56 — 22:54:42
1 min 46 secs
connect() timed out!, confirmed by Budapest, HU; Istanbul, TR
40. 23 Nov 2013 23:11:10 — 23:12:25
1 min 15 secs
connect() timed out!, confirmed by Istanbul, TR; Budapest, HU
41. 24 Nov 2013 02:35:56 — 02:38:37
2 mins 41 secs
connect() timed out!, confirmed by Istanbul, TR; Budapest, HU
42. 24 Nov 2013 04:31:04 — 04:32:40
1 min 36 secs
connect() timed out!, confirmed by Budapest, HU; Istanbul, TR
43. 24 Nov 2013 05:01:08 — 05:02:25
1 min 17 secs
connect() timed out!, confirmed by Istanbul, TR; Budapest, HU
44. 24 Nov 2013 06:31:56 — 06:33:35
1 min 39 secs
connect() timed out!, confirmed by Budapest, HU; Istanbul, TR
45. 24 Nov 2013 08:19:55 — 08:21:29
1 min 34 secs
connect() timed out!, confirmed by Budapest, HU; Istanbul, TR
46. 24 Nov 2013 12:51:56 — 12:53:30
1 min 34 secs
connect() timed out!, confirmed by Budapest, HU; Istanbul, TR
47. 24 Nov 2013 13:18:55 — 13:20:19
1 min 24 secs
connect() timed out!, confirmed by Budapest, HU; Istanbul, TR
48. 24 Nov 2013 13:44:55 — 13:46:26
1 min 31 secs
connect() timed out!, confirmed by Istanbul, TR; Budapest, HU
49. 24 Nov 2013 14:12:57 — 14:14:26
1 min 29 secs
connect() timed out!, confirmed by Istanbul, TR; Budapest, HU
50. 24 Nov 2013 14:25:56 — 14:28:26
2 mins 30 secs
connect() timed out!, confirmed by Istanbul, TR; Budapest, HU
51. 24 Nov 2013 14:44:55 — 14:46:35
1 min 40 secs
connect() timed out!, confirmed by Budapest, HU; Istanbul, TR
52. 24 Nov 2013 15:11:03 — 15:12:30
1 min 27 secs
connect() timed out!, confirmed by Istanbul, TR; Budapest, HU
53. 24 Nov 2013 16:42:55 — 16:44:26
1 min 31 secs
connect() timed out!, confirmed by Budapest, HU; Istanbul, TR
54. 24 Nov 2013 20:55:56 — 20:57:33
1 min 37 secs
connect() timed out!, confirmed by Istanbul, TR; Budapest, HU
55. 24 Nov 2013 22:18:55 — 22:20:17
1 min 22 secs
connect() timed out!, confirmed by Budapest, HU; Istanbul, TR
56. 24 Nov 2013 22:41:03 — 22:42:26
1 min 23 secs
connect() timed out!, confirmed by Istanbul, TR; Budapest, HU
25-Nov-2013
32/39
Monitive.com Monitoring Report #553
33. 57. 24 Nov 2013 22:56:55 — 23:00:40
3 mins 45 secs
connect() timed out!, confirmed by Budapest, HU; Istanbul, TR
58. 24 Nov 2013 23:04:55 — 23:06:41
1 min 46 secs
connect() timed out!, confirmed by Budapest, HU; Istanbul, TR
59. 25 Nov 2013 00:28:56 — 00:30:15
1 min 19 secs
connect() timed out!, confirmed by Istanbul, TR; Budapest, HU
Latency
Daily Averages
date
dns resolve
connect
pretransfer
first byte
download
total
173
190
162
170
152
169
173
154
0
0
0
0
544
169
159
167
0
0
0
0
869
528
494
491
21 Nov 2013
22 Nov 2013
23 Nov 2013
24 Nov 2013
All values are in milliseconds.
TCP State Daily Breakdown
Country Averages
25-Nov-2013
33/39
Monitive.com Monitoring Report #553
34. Fastest & Slowest Countries
Daily latency breakdown for the fastest and the slowest country latency.
Austria (Fastest)
25-Nov-2013
Hungary (Slowest)
34/39
Monitive.com Monitoring Report #553
35. Azerty.ro
overall uptime
total downtime
outages
average latency
5
1,085 ms
99.83% 9 mins 57 secs
Daily Summary
date
uptime (%)
downtime (t)
outages (count)
latency (ms)
99.36
99.58
100.00
100.00
3 mins 52 secs
6 mins 5 secs
-
3
2
-
1,578
1,237
906
920
21 Nov 2013
22 Nov 2013
23 Nov 2013
24 Nov 2013
Availability (Uptime)
Outage Timetable
date
21 Nov 2013
22 Nov 2013
23 Nov 2013
24 Nov 2013
hour: 00
01
02
03
04
05
06
07
08
09
10
11
12
13
14
15
16
17
18
19
2
20
21
22
23
2
6
Legend: █ no data █ no downtime █ <10 mins down █ 10+ mins down
Uptime Variation (%)
Outages
start date, time and reason
duration
1. 21 Nov 2013 19:39:23 — 19:41:29
2 mins 6 secs
Server returned HTTP code 502, confirmed by Warsaw, PL; Los Angeles, US
2. 21 Nov 2013 23:17:26 — 23:18:25
59 secs
Empty reply from server, confirmed by Warsaw, PL; London, UK
3. 21 Nov 2013 23:26:41 — 23:27:28
47 secs
couldn't connect to host, confirmed by Ankara, TR; London, UK
4. 22 Nov 2013 00:03:26 — 00:06:58
3 mins 32 secs
Empty reply from server, confirmed by London, UK; Los Angeles, US
5. 22 Nov 2013 00:22:27 — 00:25:00
2 mins 33 secs
couldn't connect to host, confirmed by Los Angeles, US; Chicago, US
25-Nov-2013
35/39
Monitive.com Monitoring Report #553
36. Latency
Daily Averages
date
dns resolve
connect
pretransfer
first byte
download
total
172
175
181
187
172
170
148
146
0
0
0
0
1,234
892
577
587
0
0
0
0
1,578
1,237
906
920
21 Nov 2013
22 Nov 2013
23 Nov 2013
24 Nov 2013
All values are in milliseconds.
TCP State Daily Breakdown
Country Averages
Fastest & Slowest Countries
Daily latency breakdown for the fastest and the slowest country latency.
Hungary (Fastest)
Chile (Slowest)
25-Nov-2013
36/39
Monitive.com Monitoring Report #553
37. MagazinulTau.ro
overall uptime
total downtime
outages
average latency
99.03%
56 mins
21
1,021 ms
Daily Summary
date
uptime (%)
downtime (t)
outages (count)
latency (ms)
96.95
98.05
99.59
99.75
18 mins 19 secs
28 mins 6 secs
5 mins 55 secs
3 mins 40 secs
6
10
3
2
2,522
1,255
540
583
21 Nov 2013
22 Nov 2013
23 Nov 2013
24 Nov 2013
Availability (Uptime)
Outage Timetable
date
hour:
21 Nov 2013
22 Nov 2013
23 Nov 2013
24 Nov 2013
00
01
02 03 04 05 06 07 08 09
10
5
2
12 13 14
15
16
17
18
2
19
20
21
22
23
0
19
11
3
3
13
1
3
2
4
Legend: █ no data █ no downtime █ <10 mins down █ 10+ mins down
Uptime Variation (%)
Outages
start date, time and reason
duration
1. 21 Nov 2013 20:59:56 — 21:02:48
2 mins 52 secs
Operation timed out after 30001 milliseconds with 0 bytes received, confirmed by Istanbul, TR; New
York, US
2. 21 Nov 2013 22:55:58 — 22:57:48
1 min 50 secs
couldn't connect to host, confirmed by Vina del Mar, CL; Warsaw, PL
3. 21 Nov 2013 22:58:58 — 23:01:48
2 mins 50 secs
Operation timed out after 30000 milliseconds with 0 bytes received, confirmed by Chicago, US; New
York, US
4. 21 Nov 2013 23:03:54 — 23:09:52
5 mins 58 secs
couldn't connect to host, confirmed by Hong Kong, HK; New York, US
5. 21 Nov 2013 23:16:56 — 23:18:36
1 min 40 secs
couldn't connect to host, confirmed by Hong Kong, HK; Moscow, RU
25-Nov-2013
37/39
Monitive.com Monitoring Report #553
38. 6. 21 Nov 2013 23:45:47 — 23:48:56
3 mins 9 secs
couldn't connect to host, confirmed by Graz, AT; Amsterdam 2, NL
7. 22 Nov 2013 00:04:46 — 00:08:54
4 mins 8 secs
couldn't connect to host, confirmed by Graz, AT; Hong Kong, HK
8. 22 Nov 2013 00:11:03 — 00:14:50
3 mins 47 secs
connect() timed out!, confirmed by Los Angeles, US; Hong Kong, HK
9. 22 Nov 2013 00:16:00 — 00:18:10
2 mins 10 secs
connect() timed out!, confirmed by Adelaide, AU; Chicago, US
10. 22 Nov 2013 00:23:08 — 00:30:43
7 mins 35 secs
connect() timed out!, confirmed by Ankara, TR; Warsaw, PL
11. 22 Nov 2013 00:42:59 — 00:44:34
1 min 35 secs
connect() timed out!, confirmed by Adelaide, AU; Chicago, US
12. 22 Nov 2013 10:08:04 — 10:10:21
2 mins 17 secs
Operation timed out after 30000 milliseconds with 0 bytes received, confirmed by Hong Kong, HK;
Moscow, RU
13. 22 Nov 2013 10:32:01 — 10:34:26
2 mins 25 secs
Operation timed out after 30000 milliseconds with 0 bytes received, confirmed by Istanbul, TR;
Moscow, RU
14. 22 Nov 2013 11:07:48 — 11:09:31
1 min 43 secs
couldn't connect to host, confirmed by Graz, AT; Amsterdam 2, NL
15. 22 Nov 2013 15:28:08 — 15:29:42
1 min 34 secs
connect() timed out!, confirmed by Ankara, TR; Istanbul, TR
16. 22 Nov 2013 19:51:49 — 19:52:41
52 secs
couldn't connect to host, confirmed by Graz, AT; Vina del Mar, CL
17. 23 Nov 2013 17:49:55 — 17:50:47
52 secs
couldn't connect to host, confirmed by Hong Kong, HK; Vina del Mar, CL
18. 23 Nov 2013 17:54:54 — 17:57:28
2 mins 34 secs
couldn't connect to host, confirmed by Hong Kong, HK; Ankara, TR
19. 23 Nov 2013 22:20:14 — 22:22:43
2 mins 29 secs
connect() timed out!, confirmed by Ankara, TR; Hong Kong, HK
20. 24 Nov 2013 01:04:54 — 01:07:26
2 mins 32 secs
connect() timed out!, confirmed by Amsterdam 2, NL; Budapest, HU
21. 24 Nov 2013 01:09:45 — 01:10:53
1 min 8 secs
couldn't connect to host, confirmed by Graz, AT; Las Vegas, US
Latency
Daily Averages
date
21 Nov 2013
22 Nov 2013
23 Nov 2013
24 Nov 2013
dns resolve
connect
pretransfer
first byte
download
total
205
161
191
195
317
254
138
152
0
0
0
0
2,000
840
211
236
0
0
0
0
2,522
1,255
540
583
All values are in milliseconds.
25-Nov-2013
38/39
Monitive.com Monitoring Report #553
39. TCP State Daily Breakdown
Country Averages
Fastest & Slowest Countries
Daily latency breakdown for the fastest and the slowest country latency.
Poland (Fastest)
25-Nov-2013
Australia (Slowest)
39/39
Monitive.com Monitoring Report #553