bgpreport

Network · data from 2026-11-12

AS213753 InterEdge B.V.

Registry name: interedge InterEdge B.V., NL · PeeringDB

2IPv4 routes 100.0% RPKI valid · 100.0% with a route object
1IPv6 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
0Low visibility seen by under 10% of full-table peers
2Route objects not announced registered with origin AS213753, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS213753, 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.
185.28.38.0/24 Valid RIR databaseRIPE 671 100% 67
209.182.102.0/24 Valid RIR databaseARIN 669 99% 68
2a00:9c20::/32 Valid RIR databaseRIPE 634 100% 69

AS-SET

PeeringDB's irr_as_set for AS213753: AS213753:AS-INTEREDGE. 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 (AS213753 isn't in the set, or no route object for AS213753 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 objectsAS213753 in itNot covered
AS213753:AS-INTEREDGE RIPE10 member sets in no database: AS-CFLD, AS-SERVOSPHERE, AS199746:AS-NEXTSERV, AS206604:AS-DOWNSTREAMS, AS213707:AS-UKNOC-DOWNSTREAM … 78627317,075 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 12 are in fix.csv.

  • AS-SET: missing member10
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
AS-SET: missing memberAS213753:AS-INTEREDGEAS213753:AS-INTEREDGE (RIPE) lists AS-CFLD; no IRR database read has it.
AS-SET: missing memberAS213753:AS-INTEREDGEAS213753:AS-INTEREDGE (RIPE) lists AS-SERVOSPHERE; no IRR database read has it.
AS-SET: missing memberAS213753:AS-INTEREDGEAS213753:AS-INTEREDGE (RIPE) lists AS199746:AS-NEXTSERV; no IRR database read has it.
AS-SET: missing memberAS213753:AS-INTEREDGEAS213753:AS-INTEREDGE (RIPE) lists AS206604:AS-DOWNSTREAMS; no IRR database read has it.
AS-SET: missing memberAS213753:AS-INTEREDGEAS213753:AS-INTEREDGE (RIPE) lists AS213707:AS-UKNOC-DOWNSTREAM; no IRR database read has it.
AS-SET: missing memberAS213753:AS-INTEREDGEAS213753:AS-INTEREDGE (RIPE) lists AS214129:AS-GSTMNT; no IRR database read has it.
AS-SET: missing memberAS213753:AS-INTEREDGEAS213753:AS-INTEREDGE (RIPE) lists AS214757:AS-PRAGUE; no IRR database read has it.
AS-SET: missing memberAS213753:AS-INTEREDGEAS213753:AS-INTEREDGE (RIPE) lists AS215110:AS-CUSTOMERS; no IRR database read has it.
AS-SET: missing memberAS213753:AS-INTEREDGEAS213753:AS-INTEREDGE (RIPE) lists AS219315:AS-EIRENIA; no IRR database read has it.
AS-SET: missing memberAS213753:AS-INTEREDGEAS213753:AS-INTEREDGE (RIPE) lists AS39753:AS-LIUXYON; no IRR database read has it.

Route objects not announced

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

38.182.0.0/20RADBNo ROA
2001:470:3cd::/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.