bgpreport

Network · data from 2026-11-12

AS2486 AFNIC (DNS Unicast)

Registry name: NIC-FR-DNS-UNICAST-PARIS2 - AFNIC (Association Francaise pour le Nommage Internet en Cooperation), FR · PeeringDB

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

Announced routes

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

192.134.0.0/22 No ROA RIR databaseRIPE 673 100% 67
192.93.0.0/24 No ROA RIR databaseRIPE 672 100% 68
2001:660:3005::/48 Valid None 633 100% 69
2001:660:3006::/48 Valid None 633 100% 69
2001:67c:2160::/48 Valid RIR databaseRIPE 634 100% 70
2001:67c:217c::/48 Valid RIR databaseRIPE 634 100% 70

AS-SET

PeeringDB's irr_as_set for AS2486: RIPE::AS-AFNIC. 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 (AS2486 isn't in the set, or no route object for AS2486 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 objectsAS2486 in itNot covered
RIPE::AS-AFNIC RIPE 3122 Yes 2

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 6 are in fix.csv.

  • ROA: none2
  • Route object: none2
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none192.134.0.0/22No ROA covers it. Add a ROA for AS2486, maxLength 22.673 of 673
ROA: none192.93.0.0/24No ROA covers it. Add a ROA for AS2486, maxLength 24.672 of 673
Route object: none2001:660:3005::/48No route object for it. Add a route object with origin AS2486 in the RIR database for the space.633 of 636
Route object: none2001:660:3006::/48No route object for it. Add a route object with origin AS2486 in the RIR database for the space.633 of 636

Route objects not announced

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

194.0.9.0/24RIPEValid
2001:678:c::/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.