bgpreport

Network · data from 2026-11-12

AS219310 R09TELECOM

Registry name: R09TELECOM EMIRASLAN EMIRASLANOV, AZ · PeeringDB

0IPv4 routes
9IPv6 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
8Low visibility seen by under 10% of full-table peers
1Route objects not announced registered with origin AS219310, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS219310, 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.
2a0b:4e07:288::/48 Valid RIR databaseRIPE 630 99% 69
2a0b:4e07:28f::/48 Valid RIR databaseRIPE 5 1%low visibility 5
2a06:9801:7d6::/48 Valid RIR databaseRIPE 1 0%low visibility 1
2a0b:4e07:280::/48 Valid RIR databaseRIPE 1 0%low visibility 1
2a0b:4e07:281::/48 Valid RIR databaseRIPE 1 0%low visibility 1
2a0b:4e07:282::/48 Valid RIR databaseRIPE 1 0%low visibility 1
2a0b:4e07:285::/48 Valid RIR databaseRIPE 1 0%low visibility 1
2a0b:4e07:287::/48 Valid RIR databaseRIPE 1 0%low visibility 1
2a0b:4e07:28a::/48 Valid RIR databaseRIPE 1 0%low visibility 1

AS-SET

PeeringDB's irr_as_set for AS219310: RIPE::AS219310. 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 (AS219310 isn't in the set, or no route object for AS219310 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 objectsAS219310 in itNot covered
RIPE::AS219310 A single AS number, not a set: AS219310 (this network), 10 route objects.

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: not announced1

Route objects not announced

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

2a14:7580:ff9d::/48RIPEValid

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.