bgpreport

Network · data from 2026-11-12

AS48190 T2 Ekaterinburg

Registry name: T2-EKATERINBURG-AS T2 Mobile LLC, RU · PeeringDB

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

Announced routes

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

89.249.150.0/24 No ROA RIR databaseRIPE 672 100% 67
89.253.0.0/18 No ROA RIR databaseRIPE 672 100% 67
109.235.88.0/21 No ROA RIR databaseRIPE 672 100% 67
176.59.192.0/19 No ROA RIR databaseRIPE 672 100% 67
90.150.64.0/20 Valid RIR databaseRIPE 672 100% 67

AS-SET

AS48190's PeeringDB record names no 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 36 are in fix.csv.

  • ROA: none4
  • Route object: not announced32
ChangePrefix or setDetailFull-table peers
ROA: none89.249.150.0/24No ROA covers it. Add a ROA for AS48190, maxLength 24.672 of 673
ROA: none89.253.0.0/18No ROA covers it. Add a ROA for AS48190, maxLength 18.672 of 673
ROA: none109.235.88.0/21No ROA covers it. Add a ROA for AS48190, maxLength 21.672 of 673
ROA: none176.59.192.0/19No ROA covers it. Add a ROA for AS48190, maxLength 19.672 of 673

Route objects not announced

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

176.59.192.0/24RIPENo ROA
176.59.193.0/24RIPENo ROA
176.59.194.0/24RIPENo ROA
176.59.195.0/24RIPENo ROA
176.59.196.0/24RIPENo ROA
176.59.197.0/24RIPENo ROA
176.59.198.0/24RIPENo ROA
176.59.199.0/24RIPENo ROA
176.59.200.0/24RIPENo ROA
176.59.201.0/24RIPENo ROA
176.59.202.0/24RIPENo ROA
176.59.203.0/24RIPENo ROA
176.59.204.0/24RIPENo ROA
176.59.205.0/24RIPENo ROA
176.59.206.0/24RIPENo ROA
176.59.207.0/24RIPENo ROA
176.59.208.0/24RIPENo ROA
176.59.209.0/24RIPENo ROA
176.59.210.0/24RIPENo ROA
176.59.211.0/24RIPENo ROA
176.59.212.0/24RIPENo ROA
176.59.213.0/24RIPENo ROA
176.59.214.0/24RIPENo ROA
176.59.215.0/24RIPENo ROA
176.59.216.0/24RIPENo ROA
176.59.217.0/24RIPENo ROA
176.59.218.0/24RIPENo ROA
176.59.219.0/24RIPENo ROA
176.59.220.0/24RIPENo ROA
176.59.221.0/24RIPENo ROA
176.59.222.0/24RIPENo ROA
176.59.223.0/24RIPENo 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.