bgpreport

Network · data from 2026-11-12

AS134832 Premier Technology Solutions

Registry name: PTS-AS-AP - Premier Technology Solutions Pty Ltd, AU · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS134832, 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.77.70.0/23 No ROA RIR databaseAPNIC, RADB 671 100% 67
103.198.107.0/24 No ROA RIR databaseAPNIC, RADB 671 100% 67
103.210.10.0/24 No ROA RIR databaseAPNIC 671 100% 67

AS-SET

AS134832'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 10 are in fix.csv.

  • ROA: none3
  • Route object: not announced7
ChangePrefix or setDetailFull-table peers
ROA: none103.77.70.0/23No ROA covers it. Add a ROA for AS134832, maxLength 23.671 of 673
ROA: none103.198.107.0/24No ROA covers it. Add a ROA for AS134832, maxLength 24.671 of 673
ROA: none103.210.10.0/24No ROA covers it. Add a ROA for AS134832, maxLength 24.671 of 673

Route objects not announced

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

2402:3e60::/32APNICNo ROA
2402:3e60::/33APNICNo ROA
2402:3e60::/34APNICNo ROA
2402:3e60:4000::/34APNICNo ROA
2402:3e60:8000::/33APNICNo ROA
2402:3e60:8000::/34APNICNo ROA
2402:3e60:c000::/34APNICNo 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.