bgpreport

Network · data from 2026-11-12

AS207803 Emenders

Registry name: EMENDERS-AS Emenders BV, NL · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS207803, 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.
2a0e:fd45:d32::/48 No ROA Nonecovered by 2a0e:fd45:d30::/44 2 0%low visibility 2
2a0e:fd45:d30::/48 No ROA Nonecovered by 2a0e:fd45:d30::/44 1 0%low visibility 1
2a0e:fd45:d30::/44 No ROA RIR databaseRADB, RIPE 2 0%low visibility 2

AS-SET

PeeringDB's irr_as_set for AS207803: AS-EMENDERS. 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 (AS207803 isn't in the set, or no route object for AS207803 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 objectsAS207803 in itNot covered
AS-EMENDERS In no IRR database read today.

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

  • ROA: none3
  • Route object: none2
  • AS-SET: not found1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none2a0e:fd45:d32::/48No ROA covers it. Add a ROA for AS207803, maxLength 48.2 of 636
Route object: none2a0e:fd45:d32::/48No route object for it. A route object for 2a0e:fd45:d30::/44 with origin AS207803 covers it (filters allowing more-specifics accept it). Add a route object with origin AS207803 in the RIR database for the space.2 of 636
ROA: none2a0e:fd45:d30::/48No ROA covers it. Add a ROA for AS207803, maxLength 48.1 of 636
Route object: none2a0e:fd45:d30::/48No route object for it. A route object for 2a0e:fd45:d30::/44 with origin AS207803 covers it (filters allowing more-specifics accept it). Add a route object with origin AS207803 in the RIR database for the space.1 of 636
ROA: none2a0e:fd45:d30::/44No ROA covers it. Add a ROA for AS207803, maxLength 44.2 of 636
AS-SET: not foundAS-EMENDERSPeeringDB names AS-EMENDERS; no IRR database read has it.

Route objects not announced

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

2602:feda:b80::/48ARINValid

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.