bgpreport

Network · data from 2026-11-12

AS13370 LocalTel Communications

Registry name: NWF-LOCALTEL-ASN-1 - Ziply Fiber, US · PeeringDB

19IPv4 routes 100.0% RPKI valid · 100.0% with a route object
1IPv6 routes 100.0% RPKI valid · 100.0% with a route object
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
0Route objects not announced registered with origin AS13370, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS13370, 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.
65.49.136.0/21 Valid RIR databaseARIN, RADB 673 100% 67
199.36.88.0/21 Valid RIR databaseARIN, RADB 673 100% 67
63.135.48.0/20 Valid RIR databaseARIN, RADB 672 100% 67
63.142.208.0/20 Valid RIR databaseARIN, RADB 672 100% 67
66.172.96.0/19 Valid RIR databaseARIN, RADB 672 100% 67
96.46.16.0/20 Valid RIR databaseARIN, RADB 672 100% 67
136.143.144.0/20 Valid RIR databaseARIN, RADB 672 100% 67
140.106.224.0/20 Valid RIR databaseARIN, RADB 672 100% 67
141.164.112.0/20 Valid RIR databaseARIN, RADB 672 100% 67
162.118.0.0/20 Valid RIR databaseARIN, RADB 672 100% 67
166.113.32.0/19 Valid RIR databaseARIN, RADB 672 100% 67
173.209.160.0/20 Valid RIR databaseARIN, RADB 672 100% 67
199.204.200.0/21 Valid RIR databaseARIN, RADB 672 100% 67
206.130.128.0/20 Valid RIR databaseARIN, RADB 672 100% 67
74.116.180.0/22 Valid RIR databaseARIN, RADB 670 100% 67
104.193.236.0/22 Valid RIR databaseARIN, RADB 670 100% 67
199.114.208.0/22 Valid RIR databaseARIN, RADB 670 100% 67
199.244.28.0/22 Valid RIR databaseARIN, RADB 670 100% 67
199.181.247.0/24 Valid RIR databaseARIN, RADB 667 99% 67
2604:e00::/32 Valid RIR databaseARIN, RADB 634 100% 67

AS-SET

PeeringDB's irr_as_set for AS13370: AS-LOCALTEL. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS13370 isn't in the set, or no route object for AS13370 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS13370 in itNot covered
AS-LOCALTEL RADB 7127 Yes 0
AFRINIC (also) 116 No 20

Fix list

Nothing to change: every route is RPKI valid with a route object in an RIR database, and every route object is announced.

Route objects not announced

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