bgpreport

Network · data from 2026-11-12

AS219418 Jan Hill

Registry name: eHILL-MEDIA Jan Hill, DE · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS219418, 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.
2a0f:6280:7010::/44 Invalid: origin None 1 0%low visibility 1
2a09:54c3:6005::/48 No ROA None 1 0%low visibility 1
2a09:54c3:6008::/48 No ROA None 1 0%low visibility 1
2a06:1283:8919::/48 Valid None 3 0%low visibility 3
2a09:54c3:600c::/48 Valid RIR databaseRIPE 636 100% 69
2a0f:6280:1600::/48 Valid RIR databaseRIPE 636 100% 69
2a0f:6280:1601::/48 Valid RIR databaseRIPE 636 100% 69
2a13:c8c4:7018::/48 Valid RIR databaseRIPE 636 100% 69
2a13:c8c4:7019::/48 Valid RIR databaseRIPE 636 100% 69
2a13:c8c4:7500::/40 Valid RIR databaseRIPE 636 100% 69

AS-SET

PeeringDB's irr_as_set for AS219418: AS219418:AS-TRANSIT. 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 (AS219418 isn't in the set, or no route object for AS219418 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 objectsAS219418 in itNot covered
AS219418:AS-TRANSIT RIPE1 member set in no database: AS215110:AS-CUSTOMERS 3215 Yes 4

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

  • ROA: origin1
  • ROA: none2
  • Route object: none4
  • AS-SET: missing member1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: origin2a0f:6280:7010::/44ROAs covering it name AS218868, AS219207, AS219208, AS219283, not AS219418. If AS219418 should announce it, add a ROA for AS219418.1 of 636
Route object: none2a0f:6280:7010::/44No route object for it. Add a route object with origin AS219418 in the RIR database for the space.1 of 636
ROA: none2a09:54c3:6005::/48No ROA covers it. Add a ROA for AS219418, maxLength 48.1 of 636
Route object: none2a09:54c3:6005::/48No route object for it. Add a route object with origin AS219418 in the RIR database for the space.1 of 636
ROA: none2a09:54c3:6008::/48No ROA covers it. Add a ROA for AS219418, maxLength 48.1 of 636
Route object: none2a09:54c3:6008::/48No route object for it. Add a route object with origin AS219418 in the RIR database for the space.1 of 636
Route object: none2a06:1283:8919::/48No route object for it. Add a route object with origin AS219418 in the RIR database for the space.3 of 636
AS-SET: missing memberAS219418:AS-TRANSITAS219418:AS-TRANSIT (RIPE) lists AS215110:AS-CUSTOMERS; no IRR database read has it.

Route objects not announced

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

2a02:2fc0:1::/48RIPEValid
2a09:54c3:616f::/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.