bgpreport

Network · data from 2026-11-12

AS55120 TVIFIBER

Registry name: TVIFIBER - Tallahatchie Valley Internet Services, LLC, US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS55120, 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.

107.151.32.0/24 Valid Nonecovered by 107.151.32.0/21 2 0%low visibility 2
152.86.16.0/20 Valid RIR databaseARIN 673 100% 67
216.245.96.0/19 Valid RIR databaseARIN 673 100% 67
107.151.32.0/20 Valid RIR databaseARIN 671 100% 67

AS-SET

AS55120'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 13 are in fix.csv.

  • Route object: none1
  • Route object: not announced12
ChangePrefix or setDetailFull-table peers
Route object: none107.151.32.0/24No route object for it. A route object for 107.151.32.0/21 with origin AS55120 covers it (filters allowing more-specifics accept it). Add a route object with origin AS55120 in the RIR database for the space.2 of 673

Route objects not announced

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

107.151.32.0/21ARINValid
107.151.40.0/21ARINValid
152.86.16.0/21ARINValid
152.86.24.0/21ARINValid
216.245.96.0/20ARINValid
216.245.96.0/21ARINValid
216.245.104.0/21ARINValid
216.245.112.0/20ARINValid
216.245.112.0/21ARINValid
216.245.120.0/21ARINValid
2001:470:191::/48ARINValid
2602:2dc::/36ARINNo 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.