Network · data from 2026-11-12
AS29899 GEISINGER - Geisinger System Services
Registry name: GEISINGER - Geisinger System Services, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS29899, 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.
| 159.240.131.0/24 | No ROA | Other origin onlycovered by 159.240.0.0/16 | 672 100% |
| 159.240.0.0/16 | No ROA | Other IRR onlyALTDB | 671 100% |
| 2620:112:c000::/40 | No ROA | RIR databaseARIN | 634 100% |
AS-SET
AS29899 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 6 are in fix.csv.
- ROA: none3
- Route object: none1
- Route object: RIR1
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 159.240.131.0/24 | No ROA covers it. Add a ROA for AS29899, maxLength 24. |
| Route object: none | 159.240.131.0/24 | Route objects for it name AS198949. A route object for 159.240.0.0/16 with origin AS29899 covers it (filters allowing more-specifics accept it). Add a route object with origin AS29899 in the RIR database for the space. |
| ROA: none | 159.240.0.0/16 | No ROA covers it. Add a ROA for AS29899, maxLength 16. |
| Route object: RIR | 159.240.0.0/16 | Route object only in ALTDB. Add it in the RIR database for the space. |
| ROA: none | 2620:112:c000::/40 | No ROA covers it. Add a ROA for AS29899, maxLength 40. |
Route objects not announced
Route objects with origin AS29899 whose prefix no peer sees AS29899 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2620:37::/48 | ARIN | No 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.