bgpreport

Network · data from 2026-11-12

AS54989 DUNCAN-TV - DUNCAN TELECOMMUNICATIONS LLC

Registry name: DUNCAN-TV - DUNCAN TELECOMMUNICATIONS LLC, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS54989, 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.
198.168.37.0/24 No ROA Nonecovered by 198.168.32.0/21 670 100% 67
64.17.97.0/24 Valid RIR databaseARIN, RADB 670 100% 68
64.17.119.0/24 Valid RIR databaseARIN, RADB 670 100% 68
207.136.204.0/24 Valid RIR databaseARIN, RADB 670 100% 68
209.198.81.0/24 Valid RIR databaseARIN, RADB 670 100% 68
216.114.149.0/24 Valid RIR databaseARIN, RADB 670 100% 68
216.114.178.0/24 Valid RIR databaseARIN, RADB 670 100% 68
216.114.179.0/24 Valid RIR databaseARIN, RADB 670 100% 68

AS-SET

AS54989 isn't in PeeringDB, where networks name their 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 5 are in fix.csv.

  • ROA: none1
  • Route object: none1
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none198.168.37.0/24No ROA covers it. Add a ROA for AS54989, maxLength 24.670 of 673
Route object: none198.168.37.0/24No route object for it. A route object for 198.168.32.0/21 with origin AS54989 covers it (filters allowing more-specifics accept it). Add a route object with origin AS54989 in the RIR database for the space.670 of 673

Route objects not announced

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

38.56.64.0/22RADBNo ROA
198.168.32.0/21RADBNo ROA
206.84.88.0/22RADBNo 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.