bgpreport

Network · data from 2026-11-12

AS58610 Telnet Telecommunication Limited

Registry name: TELNET-AS-AP - Telnet Telecommunication Limited, NZ · PeeringDB

21IPv4 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
2Low visibility seen by under 10% of full-table peers
4Route objects not announced registered with origin AS58610, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS58610, 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.76.205.0/24 Valid RIR databaseAPNIC, RADB 673 100% 68
103.76.247.0/24 Valid RIR databaseAPNIC, RADB 673 100% 68
103.77.4.0/23 Valid RIR databaseAPNIC, RADB 673 100% 68
116.12.56.0/21 Valid RIR databaseAPNIC, RADB 673 100% 68
116.206.160.0/24 Valid RIR databaseAPNIC 673 100% 68
116.206.161.0/24 Valid RIR databaseAPNIC 673 100% 68
116.206.162.0/24 Valid RIR databaseAPNIC 673 100% 68
116.206.163.0/24 Valid RIR databaseAPNIC 673 100% 68
103.77.4.0/24 Valid RIR databaseAPNIC 672 100% 68
116.12.57.0/24 Valid RIR databaseAPNIC, RADB 672 100% 68
116.12.59.0/24 Valid RIR databaseAPNIC, RADB 672 100% 68
116.12.60.0/24 Valid RIR databaseAPNIC, RADB 672 100% 68
116.12.61.0/24 Valid RIR databaseAPNIC, RADB 672 100% 68
116.12.62.0/24 Valid RIR databaseAPNIC, RADB 672 100% 68
116.12.56.0/24 Valid RIR databaseAPNIC, RADB 668 99% 67
116.12.63.0/24 Valid RIR databaseAPNIC 668 99% 67
116.12.58.0/24 Valid RIR databaseAPNIC 117 17% 37
103.77.5.0/24 Valid RIR databaseAPNIC 115 17% 37
116.206.160.0/22 Valid RIR databaseAPNIC 115 17% 37
116.206.160.0/23 Valid RIR databaseAPNIC, RADB 2 0%low visibility 3
116.206.162.0/23 Valid RIR databaseAPNIC, RADB 2 0%low visibility 3

AS-SET

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

  • Route object: not announced4

Route objects not announced

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

116.12.56.0/23APNICValid
116.12.58.0/23APNICValid
116.12.60.0/23APNICValid
116.12.62.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.