bgpreport

Network · data from 2026-11-12

AS213622 Falcon Network

Registry name: FALCON Falcon FZE LLC, AE · PeeringDB

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

Announced routes

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

82.39.105.0/24 Valid RIR databaseRADB, RIPE 668 99% 67
2a14:9d00::/29 Valid RIR databaseRIPE 635 100% 67
2a14:9d07:110::/44 Valid RIR databaseRIPE 2 0%low visibility 2

AS-SET

PeeringDB's irr_as_set for AS213622: AS213622:AS-FALCON. 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 (AS213622 isn't in the set, or no route object for AS213622 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 objectsAS213622 in itNot covered
AS213622:AS-FALCON RIPE4 member sets in no database: AS199746:AS-NEXTSERV, AS214757:AS-PRAGUE, AS215110:AS-CUSTOMERS, AS39753:AS-LIUXYON 3181347,490 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 11 are in fix.csv.

  • AS-SET: missing member4
  • Route object: not announced7
ChangePrefix or setDetailFull-table peers
AS-SET: missing memberAS213622:AS-FALCONAS213622:AS-FALCON (RIPE) lists AS199746:AS-NEXTSERV; no IRR database read has it.
AS-SET: missing memberAS213622:AS-FALCONAS213622:AS-FALCON (RIPE) lists AS214757:AS-PRAGUE; no IRR database read has it.
AS-SET: missing memberAS213622:AS-FALCONAS213622:AS-FALCON (RIPE) lists AS215110:AS-CUSTOMERS; no IRR database read has it.
AS-SET: missing memberAS213622:AS-FALCONAS213622:AS-FALCON (RIPE) lists AS39753:AS-LIUXYON; no IRR database read has it.

Route objects not announced

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

23.130.28.0/24ARINValid
64.112.99.0/24ARIN, RADBValid
85.209.223.0/24RIPEInvalid: origin
92.62.247.0/24RADB, RIPEValid
185.121.69.0/24RIPEValid
2a14:9d07::/44RIPEValid
2a14:9d07:100::/44RIPEValid

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.