bgpreport

Network · data from 2026-11-12

AS25627 BTS-USA - Business Telecommunications Services Inc

Registry name: BTS-USA - Business Telecommunications Services Inc, US · not in PeeringDB

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

Announced routes

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

79.170.66.0/27 Invalid: maxLength Nonecovered by 79.170.66.0/24 1 0%low visibility 1
79.170.66.64/27 Invalid: maxLength Nonecovered by 79.170.66.0/24 1 0%low visibility 1
87.237.80.0/23 Valid Nonecovered by 87.237.80.0/22 670 100% 67
79.170.64.0/22 Valid RIR databaseRIPE 673 100% 67
79.170.64.0/23 Valid RIR databaseRIPE 673 100% 67
79.170.66.0/23 Valid RIR databaseRIPE 673 100% 67
79.170.68.0/22 Valid RIR databaseRIPE 673 100% 67
79.170.68.0/23 Valid RIR databaseRIPE 673 100% 67
79.170.70.0/23 Valid RIR databaseRIPE 673 100% 67
87.237.82.0/23 Valid RIR databaseRIPE 673 100% 67
87.237.82.0/24 Valid RIR databaseRIPE 673 100% 67
87.237.83.0/24 Valid RIR databaseRIPE 673 100% 67
87.237.84.0/24 Valid RIR databaseRIPE 673 100% 66
87.237.86.0/24 Valid RIR databaseRIPE 673 100% 67
87.237.80.0/24 Valid RIR databaseRIPE 671 100% 67
87.237.81.0/24 Valid RIR databaseRIPE 671 100% 67
87.237.87.0/24 Valid RIR databaseRADB, RIPE 671 100% 67

AS-SET

AS25627 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 14 are in fix.csv.

  • ROA: maxLength2
  • Route object: none3
  • Route object: not announced9
ChangePrefix or setDetailFull-table peers
ROA: maxLength79.170.66.0/27ROA 79.170.64.0/22 AS25627 has maxLength 22; ROA 79.170.66.0/23 AS25627 has maxLength 23; the route is a /27. Raise the maxLength, or add a ROA for 79.170.66.0/27.1 of 673
Route object: none79.170.66.0/27No route object for it. A route object for 79.170.66.0/24 with origin AS25627 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS25627 in the RIR database for the space.1 of 673
ROA: maxLength79.170.66.64/27ROA 79.170.64.0/22 AS25627 has maxLength 22; ROA 79.170.66.0/23 AS25627 has maxLength 23; the route is a /27. Raise the maxLength, or add a ROA for 79.170.66.64/27.1 of 673
Route object: none79.170.66.64/27No route object for it. A route object for 79.170.66.0/24 with origin AS25627 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS25627 in the RIR database for the space.1 of 673
Route object: none87.237.80.0/23No route object for it. A route object for 87.237.80.0/22 with origin AS25627 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25627 in the RIR database for the space.670 of 673

Route objects not announced

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

79.170.64.0/24RIPEInvalid: maxLength
79.170.65.0/24RIPEValid
79.170.66.0/24RIPEInvalid: maxLength
79.170.68.0/24RIPEInvalid: maxLength
79.170.69.0/24RIPEValid
79.170.70.0/24RIPEValid
79.170.71.0/24RIPEValid
87.237.80.0/22RIPENo ROA
193.19.106.0/23RADBNo 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.