bgpreport

Network · data from 2026-11-12

AS25679 TDC-DATA3 - Tulsa Datacenter, LLC

Registry name: TDC-DATA3 - Tulsa Datacenter, LLC, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS25679, 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.
63.210.128.0/23 No ROA None 673 100% 67
63.210.128.0/24 No ROA None 664 99% 67
50.59.65.0/24 No ROA Other IRR onlyRADB 673 100% 67
66.194.172.0/24 No ROA Other IRR onlyRADB 673 100% 67
209.12.229.0/24 No ROA Other IRR onlyRADB 673 100% 67
209.136.158.0/24 No ROA Other IRR onlyRADB 673 100% 67
174.47.170.0/24 No ROA Other IRR onlyRADB 671 100% 67
70.183.44.0/24 Valid None 673 100% 67
70.183.45.0/24 Valid None 671 100% 67

AS-SET

AS25679 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 16 are in fix.csv.

  • ROA: none7
  • Route object: none4
  • Route object: RIR5
ChangePrefix or setDetailFull-table peers
ROA: none63.210.128.0/23No ROA covers it. Add a ROA for AS25679, maxLength 23.673 of 673
Route object: none63.210.128.0/23No route object for it. Add a route object with origin AS25679 in the RIR database for the space.673 of 673
ROA: none63.210.128.0/24No ROA covers it. Add a ROA for AS25679, maxLength 24.664 of 673
Route object: none63.210.128.0/24No route object for it. Add a route object with origin AS25679 in the RIR database for the space.664 of 673
ROA: none50.59.65.0/24No ROA covers it. Add a ROA for AS25679, maxLength 24.673 of 673
Route object: RIR50.59.65.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none66.194.172.0/24No ROA covers it. Add a ROA for AS25679, maxLength 24.673 of 673
Route object: RIR66.194.172.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none209.12.229.0/24No ROA covers it. Add a ROA for AS25679, maxLength 24.673 of 673
Route object: RIR209.12.229.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none209.136.158.0/24No ROA covers it. Add a ROA for AS25679, maxLength 24.673 of 673
Route object: RIR209.136.158.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none174.47.170.0/24No ROA covers it. Add a ROA for AS25679, maxLength 24.671 of 673
Route object: RIR174.47.170.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: none70.183.44.0/24No route object for it. Add a route object with origin AS25679 in the RIR database for the space.673 of 673
Route object: none70.183.45.0/24No route object for it. Add a route object with origin AS25679 in the RIR database for the space.671 of 673

Route objects not announced

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