bgpreport

Network · data from 2026-11-12

AS133435 RWTS-AS-AP - Real World Technology Solutions Pty Ltd

Registry name: RWTS-AS-AP - Real World Technology Solutions Pty Ltd, AU · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS133435, 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.228.212.0/22 No ROA Other origin only 672 100% 67
103.228.212.0/24 Valid RIR databaseAPNIC 672 100% 67
103.228.213.0/24 Valid RIR databaseAPNIC 672 100% 67
103.228.214.0/24 Valid RIR databaseAPNIC 672 100% 67
103.228.215.0/24 Valid RIR databaseAPNIC 672 100% 67

AS-SET

AS133435 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 4 are in fix.csv.

  • ROA: none1
  • Route object: none1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none103.228.212.0/22No ROA covers it. Add a ROA for AS133435, maxLength 22.672 of 673
Route object: none103.228.212.0/22Route objects for it name AS7545, AS24130, AS45437. Add a route object with origin AS133435 in the RIR database for the space.672 of 673

Route objects not announced

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

103.228.212.0/23APNICValid
103.228.214.0/23APNICValid

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.