bgpreport

Network · data from 2026-11-12

AS32270 LD Telecommunications

Registry name: LDTEL - LD Telecommunications, Inc., US · PeeringDB

2IPv4 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
3Route objects not announced registered with origin AS32270, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS32270, 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.
74.117.24.0/21 Valid RIR databaseARIN, RADB 669 99% 67
208.65.92.0/22 Valid RIR databaseARIN, RADB 665 99% 67
2606:1d40::/32 Valid RIR databaseARIN, RADB 633 100% 67

AS-SET

PeeringDB's irr_as_set for AS32270: RADB::AS32270:AS-CONE. 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 (AS32270 isn't in the set, or no route object for AS32270 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 objectsAS32270 in itNot covered
RADB::AS32270:AS-CONE RADB1 member set in no database: AS32270:AS-LDT1126 97192,506 Yes 0

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.

  • AS-SET: missing member1
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
AS-SET: missing memberRADB::AS32270:AS-CONEAS32270:AS-CONE (RADB) lists AS32270:AS-LDT1126; no IRR database read has it.

Route objects not announced

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

74.117.24.0/24RADBValid
74.117.26.0/24RADBValid
206.165.148.0/24RADBNo 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.