bgpreport

Network · data from 2026-11-12

AS10475 Tampa Bay Access Exchange

Registry name: TBAX-AS-2025 - Tampa Bay Access Exchange LLC, US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS10475, 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.
149.112.184.0/24 No ROA None 6 1%low visibility 7
2602:f527::/40 No ROA None 6 1%low visibility 6

AS-SET

AS10475'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.

  • ROA: none2
  • Route object: none2
ChangePrefix or setDetailFull-table peers
ROA: none149.112.184.0/24No ROA covers it. Add a ROA for AS10475, maxLength 24.6 of 673
Route object: none149.112.184.0/24No route object for it. Add a route object with origin AS10475 in the RIR database for the space.6 of 673
ROA: none2602:f527::/40No ROA covers it. Add a ROA for AS10475, maxLength 40.6 of 636
Route object: none2602:f527::/40No route object for it. Add a route object with origin AS10475 in the RIR database for the space.6 of 636

Route objects not announced

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