bgpreport

Network · data from 2026-11-12

AS215734 Georgios Karampitsakis

Registry name: KARAMPITSAKIS-AS Georgios Karampitsakis, GR · PeeringDB

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

Announced routes

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

44.32.63.0/24 No ROA Other IRR onlyRADB 672 100% 66

AS-SET

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

  • ROA: none1
  • Route object: RIR1
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
ROA: none44.32.63.0/24No ROA covers it. Add a ROA for AS215734, maxLength 24.672 of 673
Route object: RIR44.32.63.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

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

2a06:de00:de10::/48RIPEValid
2a06:de00:de11::/48RIPEValid
2a06:de00:de12::/48RIPEValid
2a06:de00:de14::/48RIPENo ROA
2a06:de00:de15::/48RIPEValid
2a0e:fd45:2de0::/48RIPENo 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.