bgpreport

Network · data from 2026-11-12

AS134134 NORTHTELECOM

Registry name: WESTERN2-AS-AP - Western ICT Solutions Services, AF · PeeringDB

10IPv4 routes 90.0% RPKI valid · 90.0% with a route object
0IPv6 routes
1RPKI invalid 1 origin · 0 maxLength
0No 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 AS134134, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS134134, 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.212.160.0/24 Invalid: origin Other origin only 1 0%low visibility 1
45.65.58.0/24 Valid RIR databaseAPNIC, RADB 673 100% 66
103.53.26.0/24 Valid RIR databaseAPNIC, RADB 673 100% 66
103.53.27.0/24 Valid RIR databaseAPNIC, RADB 673 100% 66
116.204.243.0/24 Valid RIR databaseAPNIC, RADB 673 100% 67
45.126.253.0/24 Valid RIR databaseAPNIC, RADB 672 100% 66
103.53.24.0/24 Valid RIR databaseAPNIC 672 100% 66
116.204.242.0/24 Valid RIR databaseAPNIC, RADB 672 100% 66
165.99.189.0/24 Valid RIR databaseAPNIC 672 100% 66
45.65.59.0/24 Valid RIR databaseAPNIC, RADB 671 100% 66

AS-SET

AS134134'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 2 are in fix.csv.

  • ROA: origin1
  • Route object: none1
ChangePrefix or setDetailFull-table peers
ROA: origin103.212.160.0/24ROAs covering it name AS149173, not AS134134. If AS134134 should announce it, add a ROA for AS134134.1 of 673
Route object: none103.212.160.0/24Route objects for it name AS149173. Add a route object with origin AS134134 in the RIR database for the space.1 of 673

Route objects not announced

Every route object with origin AS134134 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.