bgpreport

Network · data from 2026-11-12

AS136133 SQUIXA

Registry name: SECTIONIO-AS-AP - SQUIXA PTY LIMITED, AU · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS136133, 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.
45.154.183.0/24 Valid Other IRR onlyRADB 672 100% 70
103.107.226.0/24 Valid RIR databaseAPNIC 673 100% 70
103.107.227.0/24 Valid RIR databaseAPNIC 673 100% 70

AS-SET

AS136133'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 21 are in fix.csv.

  • Route object: RIR1
  • Route object: not announced20
ChangePrefix or setDetailFull-table peers
Route object: RIR45.154.183.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

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

45.154.180.0/22RADBNo ROA
45.154.180.0/23RADBNo ROA
45.154.180.0/24RADBValid
45.154.181.0/24RADBValid
45.154.182.0/23RADBNo ROA
45.154.182.0/24RADBValid
103.81.52.0/24APNICValid
103.107.226.0/23APNIC, RADBNo ROA
209.160.100.0/22RADBValid
209.160.100.0/23RADBValid
209.160.100.0/24RADBValid
209.160.101.0/24RADBValid
209.160.102.0/23RADBValid
209.160.102.0/24RADBValid
209.160.103.0/24RADBValid
2605:6540::/32RADBNo ROA
2605:6540:1000::/36RADBNo ROA
2605:6540:1000::/40RADBNo ROA
2605:6540:1000::/44RADBNo ROA
2605:6540:1000::/48RADBNo 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.