bgpreport

Network · data from 2026-11-12

AS201269 IVANS-AS Ivans Lavrentjevs

Registry name: IVANS-AS Ivans Lavrentjevs, LV · not in PeeringDB

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

Announced routes

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

31.56.150.0/24 Invalid: origin None 2 0%low visibility 2
151.242.237.0/24 No ROA None 2 0%low visibility 1
31.59.195.0/24 Valid RIR databaseRIPE 673 100% 67
94.183.247.0/24 Valid RIR databaseRIPE 673 100% 67
94.183.245.0/24 Valid RIR databaseRIPE 672 100% 66
31.57.217.0/24 Valid RIR databaseRIPE 671 100% 68
179.236.133.0/24 Valid RIR databaseRIPE 671 100% 67
201.58.137.0/24 Valid RIR databaseRIPE 670 100% 67

AS-SET

AS201269 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 11 are in fix.csv.

  • ROA: origin1
  • ROA: none1
  • Route object: none2
  • Route object: not announced7
ChangePrefix or setDetailFull-table peers
ROA: origin31.56.150.0/24ROAs covering it name AS834, not AS201269. If AS201269 should announce it, add a ROA for AS201269.2 of 673
Route object: none31.56.150.0/24No route object for it. Add a route object with origin AS201269 in the RIR database for the space.2 of 673
ROA: none151.242.237.0/24No ROA covers it. Add a ROA for AS201269, maxLength 24.2 of 673
Route object: none151.242.237.0/24No route object for it. Add a route object with origin AS201269 in the RIR database for the space.2 of 673

Route objects not announced

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

177.3.195.0/24RIPEValid
217.60.188.0/24RIPEValid
217.60.189.0/24RIPEValid
217.60.190.0/24RIPEValid
217.60.191.0/24RIPEValid
2a0b:4e07:2a::/48RIPEValid
2a13:9500:19e::/48RIPEValid

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.