bgpreport

Network · data from 2026-11-12

AS132789 Pivotel Group Pty Limited

Registry name: PIVOTEL-AS-AP - Pivotel Group Pty Limited, AU · PeeringDB

25IPv4 routes 96.0% RPKI valid · 96.0% with a route object
3IPv6 routes 100.0% RPKI valid · 100.0% with a route object
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
6Route objects not announced registered with origin AS132789, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS132789, 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.
203.105.200.0/24 No ROA None 672 100% 67
203.105.192.0/24 Valid RIR databaseAPNIC 672 100% 67
203.105.194.0/24 Valid RIR databaseAPNIC 672 100% 67
203.105.195.0/24 Valid RIR databaseAPNIC 672 100% 67
203.105.198.0/24 Valid RIR databaseAPNIC 672 100% 67
203.105.199.0/24 Valid RIR databaseAPNIC 672 100% 67
203.105.207.0/24 Valid RIR databaseAPNIC 672 100% 67
203.105.214.0/24 Valid RIR databaseAPNIC 672 100% 67
203.105.215.0/24 Valid RIR databaseAPNIC 672 100% 67
203.105.216.0/24 Valid RIR databaseAPNIC 672 100% 67
203.105.218.0/24 Valid RIR databaseAPNIC 672 100% 67
203.105.219.0/24 Valid RIR databaseAPNIC 672 100% 67
203.105.221.0/24 Valid RIR databaseAPNIC 672 100% 67
203.105.222.0/24 Valid RIR databaseAPNIC 672 100% 67
203.105.223.0/24 Valid RIR databaseAPNIC 672 100% 67
203.105.197.0/24 Valid RIR databaseAPNIC 671 100% 67
203.105.201.0/24 Valid RIR databaseAPNIC 671 100% 67
203.105.202.0/24 Valid RIR databaseAPNIC 671 100% 67
203.105.205.0/24 Valid RIR databaseAPNIC 671 100% 67
203.105.206.0/24 Valid RIR databaseAPNIC 671 100% 67
203.105.196.0/24 Valid RIR databaseAPNIC 670 100% 67
203.105.209.0/24 Valid RIR databaseAPNIC 670 100% 67
203.105.212.0/24 Valid RIR databaseALTDB, APNIC, BBOI 670 100% 67
203.105.213.0/24 Valid RIR databaseALTDB, APNIC, BBOI 670 100% 67
203.105.220.0/24 Valid RIR databaseAPNIC, RADB 670 100% 67
2402:3780:f001::/48 Valid RIR databaseAPNIC 636 100% 69
2402:3780:f002::/48 Valid RIR databaseAPNIC 636 100% 69
2402:3780:2::/48 Valid RIR databaseAPNIC 632 99% 67

AS-SET

AS132789'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 8 are in fix.csv.

  • ROA: none1
  • Route object: none1
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
ROA: none203.105.200.0/24No ROA covers it. Add a ROA for AS132789, maxLength 24.672 of 673
Route object: none203.105.200.0/24No route object for it. Add a route object with origin AS132789 in the RIR database for the space.672 of 673

Route objects not announced

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

203.105.193.0/24APNICValid
203.105.208.0/24APNICValid
203.105.216.0/21RADBNo ROA
203.105.217.0/24APNICValid
2402:3780::/48APNICValid
2402:3780:1000::/48APNICValid

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.