bgpreport

Network · data from 2026-11-12

AS45887 GPLHOST-AS-AP - GPLHost LLC

Registry name: GPLHOST-AS-AP - GPLHost LLC, AU · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS45887, 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.
2404:bf40:8580::/46 Invalid: origin RIR databaseAPNIC 11 2%low visibility 4
103.230.71.0/24 Valid RIR databaseALTDB, APNIC, BBOI, NTTCOM 673 100% 67
117.121.240.0/24 Valid RIR databaseAPNIC 673 100% 66
117.121.242.0/24 Valid RIR databaseAPNIC 673 100% 67
182.54.232.0/24 Valid RIR databaseAPNIC 673 100% 67
103.68.121.0/24 Valid RIR databaseAPNIC 672 100% 67
103.68.122.0/24 Valid RIR databaseAPNIC 672 100% 67
103.68.123.0/24 Valid RIR databaseAPNIC 672 100% 67
117.121.241.0/24 Valid RIR databaseAPNIC, RADB, REACH 672 100% 67
117.121.244.0/24 Valid RIR databaseAPNIC, RADB, REACH 672 100% 67
182.54.234.0/24 Valid RIR databaseAPNIC, RADB, REACH 672 100% 67

AS-SET

AS45887 isn't in PeeringDB, where networks name their 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 13 are in fix.csv.

  • ROA: origin1
  • Route object: not announced12
ChangePrefix or setDetailFull-table peers
ROA: origin2404:bf40:8580::/46ROAs covering it name AS136181, AS139084, not AS45887. If AS45887 should announce it, add a ROA for AS45887.11 of 636

Route objects not announced

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

103.68.120.0/24REACHInvalid: origin
103.206.30.0/23APNIC, RADBValid
117.121.243.0/24REACHInvalid: origin
117.121.245.0/24REACHInvalid: origin
117.121.246.0/24NTTCOM, RADBNo ROA
117.121.247.0/24REACHInvalid: origin
182.54.233.0/24REACHInvalid: origin
2403:cc00:1000::/36APNICInvalid: origin
2403:cc00:5000::/36APNICNo ROA
2403:cc00:8000::/36APNIC, RADBValid
2403:cc00:a000::/36APNICValid
2403:cc00:c000::/36APNICNo ROA

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.