bgpreport

Network · data from 2026-11-12

AS133548 RECSPL-AS-AP - RDG Electrical & Communications Solutions Pty Ltd

Registry name: RECSPL-AS-AP - RDG Electrical & Communications Solutions Pty Ltd, AU · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS133548, 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.43.178.0/23 Invalid: origin Other origin only 2 0%low visibility 2
103.235.22.0/24 No ROA Other IRR onlyALTDB 671 100% 67
103.254.5.0/24 No ROA RIR databaseAPNIC 672 100% 67

AS-SET

AS133548 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 5 are in fix.csv.

  • ROA: origin1
  • ROA: none2
  • Route object: none1
  • Route object: RIR1
ChangePrefix or setDetailFull-table peers
ROA: origin103.43.178.0/23ROAs covering it name AS135060, not AS133548. If AS133548 should announce it, add a ROA for AS133548.2 of 673
Route object: none103.43.178.0/23Route objects for it name AS135060. Add a route object with origin AS133548 in the RIR database for the space.2 of 673
ROA: none103.235.22.0/24No ROA covers it. Add a ROA for AS133548, maxLength 24.671 of 673
Route object: RIR103.235.22.0/24Route object only in ALTDB. Add it in the RIR database for the space.671 of 673
ROA: none103.254.5.0/24No ROA covers it. Add a ROA for AS133548, maxLength 24.672 of 673

Route objects not announced

Every route object with origin AS133548 is announced.

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.