bgpreport

Network · data from 2026-11-12

AS204800 hosting.com SGP1

Registry name: WHG-SGP WHG Hosting Services Ltd, GB · PeeringDB

25IPv4 routes 100.0% RPKI valid · 96.0% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
0No ROA 1 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
17Route objects not announced registered with origin AS204800, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS204800, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.
181.224.148.0/24 Valid Nonecovered by 181.224.148.0/22 673 100% 67
65.98.12.0/24 Valid RIR databaseRIPE 673 100% 67
65.98.32.0/24 Valid RIR databaseRIPE 673 100% 67
67.209.120.0/21 Valid RIR databaseARIN 673 100% 67
85.187.128.0/21 Valid RIR databaseRIPE 673 100% 67
45.120.148.0/22 Valid RIR databaseAPNIC 671 100% 67
69.48.139.0/24 Valid RIR databaseARIN 671 100% 67
69.48.188.0/22 Valid RIR databaseARIN 671 100% 67
85.187.128.0/22 Valid RIR databaseRIPE 671 100% 67
103.138.189.0/24 Valid RIR databaseRIPE 671 100% 67
103.204.130.0/23 Valid RIR databaseARIN 671 100% 67
103.227.176.0/22 Valid RIR databaseAPNIC 671 100% 67
185.149.112.0/22 Valid RIR databaseRIPE 671 100% 67
185.151.48.0/22 Valid RIR databaseRIPE 671 100% 67
185.160.65.0/24 Valid RIR databaseRIPE 671 100% 67
192.250.228.0/24 Valid RIR databaseRIPE 671 100% 67
192.250.235.0/24 Valid RIR databaseRIPE 671 100% 67
198.38.91.0/24 Valid RIR databaseRIPE 671 100% 67
209.42.27.0/24 Valid RIR databaseRIPE 671 100% 67
209.124.95.0/24 Valid RIR databaseARIN 671 100% 67
216.67.230.0/24 Valid RIR databaseRIPE 671 100% 67
216.137.184.0/23 Valid RIR databaseARIN 671 100% 67
190.92.136.0/22 Valid RIR databaseARIN 670 100% 67
190.92.184.0/22 Valid RIR databaseARIN 670 100% 67
200.69.20.0/22 Valid RIR databaseARIN 670 100% 67

AS-SET

AS204800's PeeringDB record names no AS-SET.

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 18 are in fix.csv.

  • Route object: none1
  • Route object: not announced17
ChangePrefix or setDetailFull-table peers
Route object: none181.224.148.0/24No route object for it. A route object for 181.224.148.0/22 with origin AS204800 covers it (filters allowing more-specifics accept it). Add a route object with origin AS204800 in the RIR database for the space.673 of 673

Route objects not announced

Route objects with origin AS204800 whose prefix no peer sees AS204800 announce. Many are kept on purpose (backup routes, space announced only in some places).

45.120.148.0/23APNICValid
45.120.148.0/24APNICValid
45.120.149.0/24APNICValid
45.120.150.0/23APNICValid
45.120.150.0/24APNICValid
45.120.151.0/24APNICValid
103.227.176.0/23APNICValid
103.227.176.0/24APNICValid
103.227.177.0/24APNICValid
103.227.178.0/23APNICValid
103.227.178.0/24APNICValid
103.227.179.0/24APNICValid
114.129.156.0/22RIPENo ROA
181.224.148.0/22ARINValid
181.224.152.0/22ARINValid
181.224.156.0/22ARINValid
190.92.145.0/24ARINValid

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.