bgpreport

Network · data from 2026-11-12

AS6907 EBAY-DE-AS eBay Marketplaces GmbH

Registry name: EBAY-DE-AS eBay Marketplaces GmbH, CH · not in PeeringDB

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

Announced routes

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

216.113.167.0/24 No ROA None 670 100% 67
93.94.41.0/24 No ROA Other IRR onlyRADB 670 100% 66

AS-SET

AS6907 isn't in PeeringDB, where networks name their AS-SET.

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

  • ROA: none2
  • Route object: none1
  • Route object: RIR1
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
ROA: none216.113.167.0/24No ROA covers it. Add a ROA for AS6907, maxLength 24.670 of 673
Route object: none216.113.167.0/24No route object for it. Add a route object with origin AS6907 in the RIR database for the space.670 of 673
ROA: none93.94.41.0/24No ROA covers it. Add a ROA for AS6907, maxLength 24.670 of 673
Route object: RIR93.94.41.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673

Route objects not announced

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

93.94.40.0/21RADBNo ROA
93.94.40.0/24RADB, RIPENo ROA
93.94.42.0/24RADB, RIPENo ROA
93.94.43.0/24RADB, RIPENo ROA
195.234.136.0/24RADB, RIPENo ROA

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.