bgpreport

Network · data from 2026-11-12

AS60849 NaiTel “Aqaba Digital Hub”

Registry name: iLevant-as iLevant FZE, AE · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS60849, 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.
2a04:2ec1::/32 Valid Nonecovered by 2a04:2ec0::/29 630 99% 67
87.121.62.0/24 Valid RIR databaseRIPE 673 100% 67
176.57.52.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
185.27.116.0/22 Valid RIR databaseRIPE 673 100% 67
185.27.117.0/24 Valid RIR databaseRIPE 672 100% 67
62.72.165.0/24 Valid RIR databaseRADB, RIPE 671 100% 67
62.72.179.0/24 Valid RIR databaseRADB, RIPE 671 100% 67
62.72.186.0/24 Valid RIR databaseRADB, RIPE 671 100% 67
176.57.51.0/24 Valid RIR databaseRADB, RIPE 671 100% 67
176.57.53.0/24 Valid RIR databaseRADB, RIPE 671 100% 67
185.27.116.0/24 Valid RIR databaseRIPE 671 100% 67
185.27.118.0/24 Valid RIR databaseRIPE 671 100% 67
185.27.119.0/24 Valid RIR databaseRIPE 671 100% 67
185.40.19.0/24 Valid RIR databaseRIPE 671 100% 67
62.72.167.0/24 Valid RIR databaseRADB, RIPE 670 100% 67
185.218.85.0/24 Valid RIR databaseRIPE 670 100% 68
2a04:2ec0::/32 Valid RIR databaseRIPE 636 100% 67
2a04:2ec0::/29 Valid RIR databaseRIPE 634 100% 67

AS-SET

PeeringDB's irr_as_set for AS60849: AS-ILEVANT. 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 (AS60849 isn't in the set, or no route object for AS60849 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 objectsAS60849 in itNot covered
AS-ILEVANT RIPE 25514113,704 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 1 are in fix.csv.

  • Route object: none1
ChangePrefix or setDetailFull-table peers
Route object: none2a04:2ec1::/32No route object for it. A route object for 2a04:2ec0::/29 with origin AS60849 covers it (filters allowing more-specifics accept it). Add a route object with origin AS60849 in the RIR database for the space.630 of 636

Route objects not announced

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