bgpreport

Network · data from 2026-11-12

AS61437 Alex Escape

Registry name: ALEXESCAPE Alex Escape LLC, BG · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS61437, 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.
185.200.156.0/23 Valid Nonecovered by 185.200.156.0/22 84 12% 35
185.200.158.0/23 Valid Nonecovered by 185.200.156.0/22 84 12% 35
2a09:a941::/32 Valid Nonecovered by 2a09:a940::/29 11 2%low visibility 7
31.13.232.0/22 Valid RIR databaseRIPE 672 100% 66
185.200.156.0/22 Valid RIR databaseRIPE 672 100% 66
2a09:a940::/29 Valid RIR databaseRIPE 634 100% 69
31.13.232.0/23 Valid RIR databaseRIPE 148 22% 45
31.13.234.0/23 Valid RIR databaseRIPE 148 22% 45
31.13.232.0/24 Valid RIR databaseRIPE 2 0%low visibility 3
31.13.233.0/24 Valid RIR databaseRIPE 2 0%low visibility 3
31.13.234.0/24 Valid RIR databaseRIPE 2 0%low visibility 3
31.13.235.0/24 Valid RIR databaseRIPE 2 0%low visibility 3
185.200.156.0/24 Valid RIR databaseRIPE 2 0%low visibility 3
185.200.157.0/24 Valid RIR databaseRIPE 2 0%low visibility 3
185.200.158.0/24 Valid RIR databaseRIPE 2 0%low visibility 3
185.200.159.0/24 Valid RIR databaseRIPE 2 0%low visibility 3

AS-SET

PeeringDB's irr_as_set for AS61437: AS-ALEXESCAPE. 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 (AS61437 isn't in the set, or no route object for AS61437 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 objectsAS61437 in itNot covered
AS-ALEXESCAPE RIPE 217171 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 3 are in fix.csv.

  • Route object: none3
ChangePrefix or setDetailFull-table peers
Route object: none185.200.156.0/23No route object for it. A route object for 185.200.156.0/22 with origin AS61437 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61437 in the RIR database for the space.84 of 673
Route object: none185.200.158.0/23No route object for it. A route object for 185.200.156.0/22 with origin AS61437 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61437 in the RIR database for the space.84 of 673
Route object: none2a09:a941::/32No route object for it. A route object for 2a09:a940::/29 with origin AS61437 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61437 in the RIR database for the space.11 of 636

Route objects not announced

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