bgpreport

Network · data from 2026-11-12

AS202665 SMSHW SMShighway Limited

Registry name: SMSHW SMShighway Limited, GB · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS202665, 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.
91.206.65.0/24 Valid Nonecovered by 91.206.64.0/23 3 0%low visibility 3
91.206.64.0/24 Valid Nonecovered by 91.206.64.0/23 2 0%low visibility 2
185.60.200.0/24 Valid Other IRR onlyRADB 668 99% 66
91.206.64.0/23 Valid RIR databaseRIPE 2 0%low visibility 2

AS-SET

AS202665 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 3 are in fix.csv.

  • Route object: none2
  • Route object: RIR1
ChangePrefix or setDetailFull-table peers
Route object: none91.206.65.0/24No route object for it. A route object for 91.206.64.0/23 with origin AS202665 covers it (filters allowing more-specifics accept it). Add a route object with origin AS202665 in the RIR database for the space.3 of 673
Route object: none91.206.64.0/24No route object for it. A route object for 91.206.64.0/23 with origin AS202665 covers it (filters allowing more-specifics accept it). Add a route object with origin AS202665 in the RIR database for the space.2 of 673
Route object: RIR185.60.200.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673

Route objects not announced

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