bgpreport

Network · data from 2026-11-12

AS203136 Ordunet

Registry name: ordunet LLC Ordunet, GE · PeeringDB

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

Announced routes

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

5.59.0.0/23 No ROA None 2 0%low visibility 2
5.59.0.0/24 No ROA None 2 0%low visibility 2
5.59.1.0/24 No ROA None 2 0%low visibility 2
74.1.222.0/24 Valid Nonecovered by 74.1.222.0/23 672 100% 67
74.1.223.0/24 Valid Nonecovered by 74.1.222.0/23 671 100% 67
2a0e:2700::/32 Valid Nonecovered by 2a0e:2700::/29 635 100% 67
2a0e:2701::/32 Valid Nonecovered by 2a0e:2700::/29 635 100% 67
2a0e:2702::/32 Valid Nonecovered by 2a0e:2700::/29 635 100% 67
2a0e:2703::/32 Valid Nonecovered by 2a0e:2700::/29 635 100% 67
85.117.53.0/24 Valid RIR databaseRIPE 673 100% 67
185.143.176.0/22 Valid RIR databaseRIPE 673 100% 67
185.143.176.0/24 Valid RIR databaseRIPE 673 100% 67
185.143.177.0/24 Valid RIR databaseRIPE 673 100% 67
185.143.178.0/24 Valid RIR databaseRIPE 673 100% 67
185.143.179.0/24 Valid RIR databaseRIPE 673 100% 67
74.1.222.0/23 Valid RIR databaseARIN, RADB 672 100% 67
2a0e:2700::/29 Valid RIR databaseRIPE 634 100% 67

AS-SET

PeeringDB's irr_as_set for AS203136: AS-ORDUNET. 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 (AS203136 isn't in the set, or no route object for AS203136 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 objectsAS203136 in itNot covered
AS-ORDUNET RIPE 118 Yes 3

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

  • ROA: none3
  • Route object: none9
ChangePrefix or setDetailFull-table peers
ROA: none5.59.0.0/23No ROA covers it. Add a ROA for AS203136, maxLength 23.2 of 673
Route object: none5.59.0.0/23No route object for it. Add a route object with origin AS203136 in the RIR database for the space.2 of 673
ROA: none5.59.0.0/24No ROA covers it. Add a ROA for AS203136, maxLength 24.2 of 673
Route object: none5.59.0.0/24No route object for it. Add a route object with origin AS203136 in the RIR database for the space.2 of 673
ROA: none5.59.1.0/24No ROA covers it. Add a ROA for AS203136, maxLength 24.2 of 673
Route object: none5.59.1.0/24No route object for it. Add a route object with origin AS203136 in the RIR database for the space.2 of 673
Route object: none74.1.222.0/24No route object for it. A route object for 74.1.222.0/23 with origin AS203136 covers it (filters allowing more-specifics accept it). Add a route object with origin AS203136 in the RIR database for the space.672 of 673
Route object: none74.1.223.0/24No route object for it. A route object for 74.1.222.0/23 with origin AS203136 covers it (filters allowing more-specifics accept it). Add a route object with origin AS203136 in the RIR database for the space.671 of 673
Route object: none2a0e:2700::/32No route object for it. A route object for 2a0e:2700::/29 with origin AS203136 covers it (filters allowing more-specifics accept it). Add a route object with origin AS203136 in the RIR database for the space.635 of 636
Route object: none2a0e:2701::/32No route object for it. A route object for 2a0e:2700::/29 with origin AS203136 covers it (filters allowing more-specifics accept it). Add a route object with origin AS203136 in the RIR database for the space.635 of 636
Route object: none2a0e:2702::/32No route object for it. A route object for 2a0e:2700::/29 with origin AS203136 covers it (filters allowing more-specifics accept it). Add a route object with origin AS203136 in the RIR database for the space.635 of 636
Route object: none2a0e:2703::/32No route object for it. A route object for 2a0e:2700::/29 with origin AS203136 covers it (filters allowing more-specifics accept it). Add a route object with origin AS203136 in the RIR database for the space.635 of 636

Route objects not announced

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