| T2 IP Qty | T2 Server Qty |
|---|---|
| 1938 | 64 |
| Total Incidents | Total Downtime | Affected IP | Affected Server | Fail Incidents | Fail Time | Degrade Incidents | Degrade Time |
|---|---|---|---|---|---|---|---|
| 82,787 | 480,520 min (8,008.7 hrs) | 1,800 | 62 | 81,982 | 478,784 min (7,979.7 hrs) | 805 | 1,736 min (28.9 hrs) |
| No | IP | Zone | Server | Start Time | End Time | Type | Downtime | Remarks |
|---|---|---|---|---|---|---|---|---|
| 1 | 103.250.7.26 | Fuya | Gigabit_Japan_103.250.7.4_60 IP_250M Burstable to 500M (China) (Y3) change to 200M Burstable to 400M on April2025 | 2025-10-01 12:50:00 | 2025-10-06 00:00:00 | Fail | 6,430 min (107.2 hrs) | Gigabit was attacked by a large-scale network scanning attack, affecting IP range 103.250.7.0/24 |
| 2 | 103.250.7.36 | Fuya | Gigabit_Japan_103.250.7.4_60 IP_250M Burstable to 500M (China) (Y3) change to 200M Burstable to 400M on April2025 | 2025-10-01 13:08:00 | 2025-10-02 21:22:00 | Fail | 1,934 min (32.2 hrs) | - same as above - |
| 3 | 103.250.7.136 | Fuya | Gigabit_Japan_103.250.7.4_60 IP_250M Burstable to 500M (China) (Y3) change to 200M Burstable to 400M on April2025 | 2025-10-01 13:08:00 | 2025-10-02 21:22:00 | Fail | 1,934 min (32.2 hrs) | - same as above - |
| 4 | 103.250.7.99 | Fuya | Gigabit_Japan_103.250.7.65_60 IP_200M Burstable to 400M (China) (Y4) | 2025-10-01 13:08:00 | 2025-10-02 21:20:00 | Fail | 1,932 min (32.2 hrs) | - same as above - |
| 5 | 103.250.7.91 | Fuya | Gigabit_Japan_103.250.7.65_60 IP_200M Burstable to 400M (China) (Y4) | 2025-10-01 13:06:00 | 2025-10-02 21:18:00 | Fail | 1,932 min (32.2 hrs) | - same as above - |
| 6 | 103.250.7.66 | Fuya | Gigabit_Japan_103.250.7.65_60 IP_200M Burstable to 400M (China) (Y4) | 2025-10-01 13:08:00 | 2025-10-02 21:20:00 | Fail | 1,932 min (32.2 hrs) | - same as above - |
| 7 | 103.250.7.35 | Fuya | Gigabit_Japan_103.250.7.4_60 IP_250M Burstable to 500M (China) (Y3) change to 200M Burstable to 400M on April2025 | 2025-10-01 13:08:00 | 2025-10-02 21:20:00 | Fail | 1,932 min (32.2 hrs) | - same as above - |
| 8 | 103.250.7.167 | Main2 | Gigabit_Japan_103.250.7.144_34 IP_150M burstable to 300M | 2025-10-01 13:08:00 | 2025-10-02 21:20:00 | Fail | 1,932 min (32.2 hrs) | - same as above - |
| 9 | 103.250.7.164 | Main2 | Gigabit_Japan_103.250.7.144_34 IP_150M burstable to 300M | 2025-10-01 13:08:00 | 2025-10-02 21:20:00 | Fail | 1,932 min (32.2 hrs) | - same as above - |
| 10 | 103.250.7.161 | Main2 | Gigabit_Japan_103.250.7.144_34 IP_150M burstable to 300M | 2025-10-01 13:08:00 | 2025-10-02 21:20:00 | Fail | 1,932 min (32.2 hrs) | - same as above - |
| No | IP | Zone | Server | Downtime | Availability | Fail Incidents | Fail Time | Degrade Incidents | Degrade Time | Remarks |
|---|---|---|---|---|---|---|---|---|---|---|
| 1 | 103.250.7.26 | Fuya | Gigabit_Japan_103.250.7.4_60 IP_250M Burstable to 500M (China) (Y3) change to 200M Burstable to 400M on April2025 | 6,440 min (107.3 hrs) | 40.37 % | 4 | 6,436 min | 2 | 4 min | Gigabit was attacked by a large-scale network scanning attack, affecting IP range 103.250.7.0/24 |
| 2 | 103.250.7.176 | Main2 | Gigabit_Japan_103.250.7.144_34 IP_150M burstable to 300M | 2,118 min (35.3 hrs) | 80.39 % | 61 | 2,118 min | 0 | 0 min | - same as above - |
| 3 | 103.250.7.167 | Main2 | Gigabit_Japan_103.250.7.144_34 IP_150M burstable to 300M | 2,118 min (35.3 hrs) | 80.39 % | 60 | 2,056 min | 1 | 62 min | - same as above - |
| 4 | 103.250.7.164 | Main2 | Gigabit_Japan_103.250.7.144_34 IP_150M burstable to 300M | 2,106 min (35.1 hrs) | 80.50 % | 53 | 2,042 min | 2 | 64 min | - same as above - |
| 5 | 103.250.7.178 | Fuya | Gigabit_Japan_103.250.7.65_60 IP_200M Burstable to 400M (China) (Y4) | 2,090 min (34.8 hrs) | 80.65 % | 77 | 2,090 min | 0 | 0 min | - same as above - |
| 6 | 103.250.7.48 | Fuya | Gigabit_Japan_103.250.7.4_60 IP_250M Burstable to 500M (China) (Y3) change to 200M Burstable to 400M on April2025 | 2,086 min (34.8 hrs) | 80.69 % | 71 | 2,080 min | 3 | 6 min | - same as above - |
| 7 | 103.250.7.125 | Fuya | Gigabit_Japan_103.250.7.65_60 IP_200M Burstable to 400M (China) (Y4) | 2,080 min (34.7 hrs) | 80.74 % | 72 | 2,080 min | 0 | 0 min | - same as above - |
| 8 | 103.250.7.185 | Fuya | Gigabit_Japan_103.250.7.4_60 IP_250M Burstable to 500M (China) (Y3) change to 200M Burstable to 400M on April2025 | 2,078 min (34.6 hrs) | 80.76 % | 70 | 2,078 min | 0 | 0 min | - same as above - |
| 9 | 103.250.7.153 | Main2 | Gigabit_Japan_103.250.7.144_34 IP_150M burstable to 300M | 2,078 min (34.6 hrs) | 80.76 % | 65 | 2,074 min | 2 | 4 min | - same as above - |
| 10 | 103.250.7.182 | Fuya | Gigabit_Japan_103.250.7.4_60 IP_250M Burstable to 500M (China) (Y3) change to 200M Burstable to 400M on April2025 | 2,076 min (34.6 hrs) | 80.78 % | 70 | 2,076 min | 0 | 0 min | - same as above - |
| No | Zone | Server | IP Count | Total Down Time | Fail Incidents | Fail Time | Degrade Incidents | Degrade Time | Remarks |
|---|---|---|---|---|---|---|---|---|---|
| 1 | Fuya | Gigabit_Japan_103.250.7.4_60 IP_250M Burstable to 500M (China) (Y3) change to 200M Burstable to 400M on April2025 | 60 | 127,656 min (2,127.6 hrs) | 3,431 | 127,578 min | 39 | 78 min | Gigabit was attacked by a large-scale network scanning attack, affecting IP range 103.250.7.0/24 |
| 2 | Fuya | Gigabit_Japan_103.250.7.65_60 IP_200M Burstable to 400M (China) (Y4) | 59 | 121,302 min (2,021.7 hrs) | 3,485 | 121,280 min | 11 | 22 min | Gigabit was attacked by a large-scale network scanning attack, affecting IP range 103.250.7.0/24 |
| 3 | Main2 | Gigabit_Japan_103.250.7.144_34 IP_150M burstable to 300M | 34 | 69,876 min (1,164.6 hrs) | 1,912 | 69,680 min | 38 | 196 min | Gigabit was attacked by a large-scale network scanning attack, affecting IP range 103.250.7.0/24 |
| 4 | Main | DataPlugs_Japan_Tokyo_157.85.229.2 61 IP_INT:250M | 61 | 30,338 min (505.6 hrs) | 13,601 | 29,888 min | 223 | 450 min | Bad & Unstable |
| 5 | Fuya | DataPlugs_Japan_Tokyo_157.85.229.66 61 IP_INT:250M | 61 | 29,276 min (487.9 hrs) | 13,276 | 29,078 min | 99 | 198 min | Bad & Unstable |
| 6 | Fuya | Simcentric_Japan_157.85.230.66_58 IP_250M INTL (Y4) | 58 | 24,994 min (416.6 hrs) | 11,250 | 24,884 min | 55 | 110 min | Bad & Unstable |
| 7 | Main | Simcentric_Japan_157.85.230.2_58 EIP_250 Mbps INTL | 58 | 24,216 min (403.6 hrs) | 10,878 | 24,084 min | 66 | 132 min | Bad & Unstable |
| 8 | Fuya | Simcentric_Hong Kong_112.121.188.242_26 IP_100M INTL + 25M CN2 (Y3) | 26 | 8,720 min (145.3 hrs) | 3,949 | 8,710 min | 5 | 10 min | Bad & Unstable |
| 9 | Fuya | DataPlugs_Hong Kong_111.68.11.194 29 IP_INT:100M CN2:25M (Y3) | 29 | 6,222 min (103.7 hrs) | 2,908 | 6,136 min | 43 | 86 min | Bad but slightly better |
| 10 | Main | Simcentric_Hong Kong_216.118.224.162_29 EIP_100 Mbps INTL + 25 Mbps CN2 | 29 | 4,718 min (78.6 hrs) | 2,229 | 4,698 min | 10 | 20 min | Bad but slightly better |