bgpreport

Network · data from 2026-11-12

AS218346 Serverdunyam

Registry name: Serverdunyam Nariman Mammadov, AZ · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS218346, 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:88::/48 No ROA RIR databaseRIPE 636 100% 69
2a0b:4e07:2e0::/44 Valid RIR databaseRIPE 636 100% 69
2a0b:4e07:2ea::/48 Valid RIR databaseRIPE 636 100% 69
2a0b:4e07:2eb::/48 Valid RIR databaseRIPE 636 100% 69
2a0b:4e07:2ec::/48 Valid RIR databaseRIPE 636 100% 69
2a0b:4e07:2ed::/48 Valid RIR databaseRIPE 636 100% 69
2a0b:4e07:2ee::/48 Valid RIR databaseRIPE 636 100% 69
2a0b:4e07:2ef::/48 Valid RIR databaseRIPE 636 100% 69
2a0b:4e07:2e1::/48 Valid RIR databaseRIPE 635 100% 69
2a0b:4e07:2e2::/48 Valid RIR databaseRIPE 635 100% 69
2a0b:4e07:2e3::/48 Valid RIR databaseRIPE 635 100% 69
2a0b:4e07:2e4::/48 Valid RIR databaseRIPE 635 100% 69
2a0b:4e07:2e5::/48 Valid RIR databaseRIPE 635 100% 69
2a0b:4e07:2e6::/48 Valid RIR databaseRIPE 635 100% 69
2a0b:4e07:2e8::/48 Valid RIR databaseRIPE 635 100% 69
2a0b:4e07:2e9::/48 Valid RIR databaseRIPE 635 100% 69
2a0b:4e07:2e7::/48 Valid RIR databaseRIPE 1 0%low visibility 1

AS-SET

PeeringDB's irr_as_set for AS218346: RIPE::AS218346:AS-SERVERDUNYAM. 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 (AS218346 isn't in the set, or no route object for AS218346 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 objectsAS218346 in itNot covered
RIPE::AS218346:AS-SERVERDUNYAM RIPE 91214 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.

  • ROA: none1
ChangePrefix or setDetailFull-table peers
ROA: none2a0b:4e07:88::/48No ROA covers it. Add a ROA for AS218346, maxLength 48.636 of 636

Route objects not announced

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