Network · data from 2026-11-12
AS50518 gl G&L Geissendoerfer & Leschinsky GmbH
Registry name: gl G&L Geissendoerfer & Leschinsky GmbH, DE · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS50518, 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.
| 83.231.152.0/24 | Valid | Other IRR onlyNTTCOM | 673 100% |
| 45.94.248.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 45.94.251.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 2a11:7400:f2::/48 | Valid | RIR databaseNTTCOM, RIPE | 633 100% |
| 45.94.250.0/23 | Valid | RIR databaseRIPE | 2 0%low visibility |
AS-SET
AS50518 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 7 are in fix.csv.
- Route object: RIR1
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 83.231.152.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS50518 whose prefix no peer sees AS50518 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.94.248.0/22 | RIPE | Valid |
| 45.94.248.0/23 | RIPE | Valid |
| 45.94.249.0/24 | RIPE | Valid |
| 45.94.250.0/24 | RIPE | Valid |
| 2a11:7400::/29 | RIPE | Valid |
| 2a11:7400:d1::/48 | RIPE | Valid |
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.