bgpreport

Network · data from 2026-11-12

AS198953 proton66 Proton66 OOO

Registry name: proton66 Proton66 OOO, RU · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS198953, 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.
37.77.150.0/24 No ROA RIR databaseRIPE 651 97% 65
176.120.22.0/24 No ROA RIR databaseRIPE 651 97% 65
193.143.1.0/24 No ROA RIR databaseRIPE 651 97% 65

AS-SET

AS198953 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.

  • ROA: none3
ChangePrefix or setDetailFull-table peers
ROA: none37.77.150.0/24No ROA covers it. Add a ROA for AS198953, maxLength 24.651 of 673
ROA: none176.120.22.0/24No ROA covers it. Add a ROA for AS198953, maxLength 24.651 of 673
ROA: none193.143.1.0/24No ROA covers it. Add a ROA for AS198953, maxLength 24.651 of 673

Route objects not announced

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