bgpreport

Network · data from 2026-11-12

AS45504 SPLUNKNET-PH - MCPO Box 1906

Registry name: SPLUNKNET-PH - MCPO Box 1906, PH · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS45504, 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.
103.22.158.0/24 No ROA RIR databaseAPNIC 673 100% 67
103.253.187.0/24 No ROA RIR databaseAPNIC, RADB 673 100% 67
103.22.156.0/24 No ROA RIR databaseAPNIC 672 100% 67
103.22.157.0/24 No ROA RIR databaseAPNIC 672 100% 67
103.253.184.0/24 No ROA RIR databaseAPNIC, RADB 672 100% 67
103.253.186.0/24 No ROA RIR databaseAPNIC, RADB 672 100% 67
103.22.159.0/24 No ROA RIR databaseAPNIC 670 100% 67
103.253.185.0/24 No ROA RIR databaseAPNIC, RADB 669 99% 67

AS-SET

AS45504 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 23 are in fix.csv.

  • ROA: none8
  • Route object: not announced15
ChangePrefix or setDetailFull-table peers
ROA: none103.22.158.0/24No ROA covers it. Add a ROA for AS45504, maxLength 24.673 of 673
ROA: none103.253.187.0/24No ROA covers it. Add a ROA for AS45504, maxLength 24.673 of 673
ROA: none103.22.156.0/24No ROA covers it. Add a ROA for AS45504, maxLength 24.672 of 673
ROA: none103.22.157.0/24No ROA covers it. Add a ROA for AS45504, maxLength 24.672 of 673
ROA: none103.253.184.0/24No ROA covers it. Add a ROA for AS45504, maxLength 24.672 of 673
ROA: none103.253.186.0/24No ROA covers it. Add a ROA for AS45504, maxLength 24.672 of 673
ROA: none103.22.159.0/24No ROA covers it. Add a ROA for AS45504, maxLength 24.670 of 673
ROA: none103.253.185.0/24No ROA covers it. Add a ROA for AS45504, maxLength 24.669 of 673

Route objects not announced

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

43.254.60.0/22NTTCOM, RADBNo ROA
103.22.156.0/22APNIC, NTTCOMNo ROA
103.22.156.0/23APNICNo ROA
103.22.158.0/23APNICNo ROA
103.253.184.0/22APNIC, NTTCOM, RADBNo ROA
103.253.184.0/23APNICNo ROA
103.253.186.0/23APNICNo ROA
123.255.224.0/21RADBNo ROA
123.255.224.0/24APNICNo ROA
123.255.225.0/24APNICNo ROA
123.255.226.0/24APNICNo ROA
123.255.227.0/24APNICNo ROA
123.255.228.0/24APNICNo ROA
123.255.229.0/24APNICNo ROA
203.148.92.0/24APNICNo 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.