bgpreport

Network · data from 2026-11-12

AS20260 SAWTEL-UC - Sawtel, Inc

Registry name: SAWTEL-UC - Sawtel, Inc, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS20260, 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.
66.37.111.0/24 Invalid: origin Other origin only 31 5%low visibility 20
66.37.106.0/23 No ROA Other origin only 669 99% 69
66.37.103.0/24 No ROA Other IRR onlyRADB 671 100% 68
66.37.104.0/23 No ROA Other IRR onlyRADB 671 100% 68
66.37.109.0/24 No ROA Other IRR onlyRADB 671 100% 68
66.37.110.0/24 No ROA Other IRR onlyRADB 671 100% 68
66.37.98.0/23 No ROA Other IRR onlyRADB 669 99% 68

AS-SET

AS20260 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 15 are in fix.csv.

  • ROA: origin1
  • ROA: none6
  • Route object: none2
  • Route object: RIR5
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: origin66.37.111.0/24ROAs covering it name AS206283, not AS20260. If AS20260 should announce it, add a ROA for AS20260.31 of 673
Route object: none66.37.111.0/24Route objects for it name AS206283. Add a route object with origin AS20260 in the RIR database for the space.31 of 673
ROA: none66.37.106.0/23No ROA covers it. Add a ROA for AS20260, maxLength 23.669 of 673
Route object: none66.37.106.0/23Route objects for it name AS16637, AS37350. Add a route object with origin AS20260 in the RIR database for the space.669 of 673
ROA: none66.37.103.0/24No ROA covers it. Add a ROA for AS20260, maxLength 24.671 of 673
Route object: RIR66.37.103.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none66.37.104.0/23No ROA covers it. Add a ROA for AS20260, maxLength 23.671 of 673
Route object: RIR66.37.104.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none66.37.109.0/24No ROA covers it. Add a ROA for AS20260, maxLength 24.671 of 673
Route object: RIR66.37.109.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none66.37.110.0/24No ROA covers it. Add a ROA for AS20260, maxLength 24.671 of 673
Route object: RIR66.37.110.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none66.37.98.0/23No ROA covers it. Add a ROA for AS20260, maxLength 23.669 of 673
Route object: RIR66.37.98.0/23Route object only in RADB. Add it in the RIR database for the space.669 of 673

Route objects not announced

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

102.22.22.0/24RADBNo 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.