bgpreport

Network · data from 2026-11-12

AS216366 Smart-tel SMART-TEL LLC

Registry name: Smart-tel SMART-TEL LLC, RU · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS216366, 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.
62.76.225.250/32 Invalid: maxLength Nonecovered by 62.76.225.0/24 3 0%low visibility 6
62.76.225.251/32 Invalid: maxLength Nonecovered by 62.76.225.0/24 3 0%low visibility 6
194.113.151.250/32 Invalid: maxLength Nonecovered by 194.113.151.0/24 3 0%low visibility 6
194.113.151.251/32 Invalid: maxLength Nonecovered by 194.113.151.0/24 3 0%low visibility 6
62.76.225.0/24 Valid RIR databaseRIPE 673 100% 66
78.142.239.0/24 Valid RIR databaseRIPE 673 100% 66
170.168.9.0/24 Valid RIR databaseRIPE 673 100% 66
194.113.151.0/24 Valid RIR databaseRIPE 673 100% 66

AS-SET

AS216366 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 8 are in fix.csv.

  • ROA: maxLength4
  • Route object: none4
ChangePrefix or setDetailFull-table peers
ROA: maxLength62.76.225.250/32ROA 62.76.225.0/24 AS216366 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 62.76.225.250/32.3 of 673
Route object: none62.76.225.250/32No route object for it. A route object for 62.76.225.0/24 with origin AS216366 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS216366 in the RIR database for the space.3 of 673
ROA: maxLength62.76.225.251/32ROA 62.76.225.0/24 AS216366 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 62.76.225.251/32.3 of 673
Route object: none62.76.225.251/32No route object for it. A route object for 62.76.225.0/24 with origin AS216366 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS216366 in the RIR database for the space.3 of 673
ROA: maxLength194.113.151.250/32ROA 194.113.151.0/24 AS216366 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 194.113.151.250/32.3 of 673
Route object: none194.113.151.250/32No route object for it. A route object for 194.113.151.0/24 with origin AS216366 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS216366 in the RIR database for the space.3 of 673
ROA: maxLength194.113.151.251/32ROA 194.113.151.0/24 AS216366 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 194.113.151.251/32.3 of 673
Route object: none194.113.151.251/32No route object for it. A route object for 194.113.151.0/24 with origin AS216366 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS216366 in the RIR database for the space.3 of 673

Route objects not announced

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