bgpreport

Network · data from 2026-11-12

AS60351 GEIBIT-AS Geib IT GmbH

Registry name: GEIBIT-AS Geib IT GmbH, DE · not in PeeringDB

5IPv4 routes 100.0% RPKI valid · 100.0% with a route object
1IPv6 routes 100.0% RPKI valid · 0.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
7Route objects not announced registered with origin AS60351, seen from no peer

Announced routes

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

2a00:8140:f000::/36 Valid Nonecovered by 2a00:8140::/32 1 0%low visibility 1
37.77.200.0/24 Valid RIR databaseRIPE 673 100% 66
37.77.203.0/24 Valid RIR databaseRIPE 673 100% 66
37.77.205.0/24 Valid RIR databaseRIPE 673 100% 66
37.77.207.0/24 Valid RIR databaseRIPE 673 100% 66
185.21.164.0/22 Valid RIR databaseRIPE 673 100% 66

AS-SET

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

  • Route object: none1
  • Route object: not announced7
ChangePrefix or setDetailFull-table peers
Route object: none2a00:8140:f000::/36No route object for it. A route object for 2a00:8140::/32 with origin AS60351 covers it (filters allowing more-specifics accept it). Add a route object with origin AS60351 in the RIR database for the space.1 of 636

Route objects not announced

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

37.77.200.0/21RIPENo ROA
37.77.202.0/24RIPEValid
37.77.204.0/24RIPEValid
37.77.206.0/24RIPEValid
2a00:8140::/32RIPENo ROA
2a00:8140::/36RIPEValid
2a00:8140:1000::/36RIPEValid

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.