bgpreport

Network · data from 2026-11-12

AS213928 INSIDENETWORKS

Registry name: INSIDENETWORKS Johannes Bauch, DE · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS213928, 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:97c0:190::/47 Valid Nonecovered by 2a0e:97c0:190::/44 632 99% 68
2a0e:97c0:190::/48 Valid RIR databaseRIPE 635 100% 68
2a0e:97c0:191::/48 Valid RIR databaseRIPE 635 100% 68
2a0e:97c0:190::/44 Valid RIR databaseRIPE 2 0%low visibility 2

AS-SET

AS213928's PeeringDB record names no 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 2 are in fix.csv.

  • Route object: none1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
Route object: none2a0e:97c0:190::/47No route object for it. A route object for 2a0e:97c0:190::/44 with origin AS213928 covers it (filters allowing more-specifics accept it). Add a route object with origin AS213928 in the RIR database for the space.632 of 636

Route objects not announced

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

2a0e:97c0:192::/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.