bgpreport

Network · data from 2026-11-12

AS41601 NEO Print, Ltd

Registry name: OBLTEL-AS NEO Print Ltd., RU · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS41601, 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.255.73.0/24 No ROA Nonecovered by 89.255.72.0/21 671 100% 68
89.255.108.0/22 No ROA RIR databaseRIPE 673 100% 66
89.255.64.0/19 No ROA RIR databaseRIPE 671 100% 68
89.255.95.0/24 No ROA RIR databaseRIPE 671 100% 68
89.255.97.0/24 No ROA RIR databaseRIPE 671 100% 68
89.255.101.0/24 No ROA RIR databaseRIPE 671 100% 68
89.255.102.0/24 No ROA RIR databaseRIPE 671 100% 68
185.93.208.0/24 No ROA RIR databaseRIPE 671 100% 68
2a02:e08::/32 No ROA RIR databaseRIPE 636 100% 69

AS-SET

PeeringDB's irr_as_set for AS41601: AS-OBLTELECOM. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS41601 isn't in the set, or no route object for AS41601 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS41601 in itNot covered
AS-OBLTELECOM RIPE 2142 Yes 0

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

  • ROA: none9
  • Route object: none1
  • Route object: not announced18
ChangePrefix or setDetailFull-table peers
ROA: none89.255.73.0/24No ROA covers it. Add a ROA for AS41601, maxLength 24.671 of 673
Route object: none89.255.73.0/24No route object for it. A route object for 89.255.72.0/21 with origin AS41601 covers it (filters allowing more-specifics accept it). Add a route object with origin AS41601 in the RIR database for the space.671 of 673
ROA: none89.255.108.0/22No ROA covers it. Add a ROA for AS41601, maxLength 22.673 of 673
ROA: none89.255.64.0/19No ROA covers it. Add a ROA for AS41601, maxLength 19.671 of 673
ROA: none89.255.95.0/24No ROA covers it. Add a ROA for AS41601, maxLength 24.671 of 673
ROA: none89.255.97.0/24No ROA covers it. Add a ROA for AS41601, maxLength 24.671 of 673
ROA: none89.255.101.0/24No ROA covers it. Add a ROA for AS41601, maxLength 24.671 of 673
ROA: none89.255.102.0/24No ROA covers it. Add a ROA for AS41601, maxLength 24.671 of 673
ROA: none185.93.208.0/24No ROA covers it. Add a ROA for AS41601, maxLength 24.671 of 673
ROA: none2a02:e08::/32No ROA covers it. Add a ROA for AS41601, maxLength 32.636 of 636

Route objects not announced

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

89.255.65.0/24RIPENo ROA
89.255.67.0/24RIPENo ROA
89.255.68.0/22RIPENo ROA
89.255.68.0/23RIPENo ROA
89.255.71.0/24RIPENo ROA
89.255.72.0/21RIPENo ROA
89.255.84.0/24RIPENo ROA
89.255.86.0/24RIPENo ROA
89.255.87.0/24RIPENo ROA
89.255.88.0/23RIPENo ROA
89.255.88.0/24RIPENo ROA
89.255.89.0/24RIPENo ROA
89.255.90.0/24RIPENo ROA
89.255.91.0/24RIPENo ROA
89.255.92.0/24RIPENo ROA
89.255.93.0/24RIPENo ROA
89.255.94.0/24RIPENo ROA
89.255.112.0/22RIPENo 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.