Network · data from 2026-11-12
AS269098 AS269098 - AbsamHost Internet Data Center
Registry name: AS269098 - AbsamHost Internet Data Center, BR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS269098, 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.
| 45.178.180.0/24 | Valid | Other IRR onlyTC | 672 100% |
| 45.178.182.0/24 | Valid | Other IRR onlyTC | 672 100% |
| 45.165.116.0/24 | Valid | Other IRR onlyRADB | 671 100% |
| 45.165.119.0/24 | Valid | Other IRR onlyTC | 669 99% |
| 45.165.118.0/24 | Valid | Other IRR onlyTC | 663 99% |
| 2804:5f6c::/35 | Valid | Other IRR onlyRADB, TC | 636 100% |
| 45.178.181.0/24 | Valid | Other IRR onlyTC | 2 0%low visibility |
| 45.178.183.0/24 | Valid | Other IRR onlyTC | 2 0%low visibility |
AS-SET
AS269098 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 22 are in fix.csv.
- Route object: RIR8
- Route object: not announced14
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 45.178.180.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 45.178.182.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 45.165.116.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 45.165.119.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 45.165.118.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:5f6c::/35 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 45.178.181.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 45.178.183.0/24 | Route object only in TC. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS269098 whose prefix no peer sees AS269098 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.165.116.0/22 | RADB, TC | Valid |
| 45.165.117.0/24 | TC | Valid |
| 45.178.180.0/22 | RADB, TC | Valid |
| 45.178.180.0/23 | RADB | Valid |
| 50.114.48.0/24 | ARIN, RADB | Valid |
| 201.11.226.0/24 | RADB, RIPE | Valid |
| 216.185.39.0/24 | ARIN | Invalid: origin |
| 2804:5f6c::/32 | RADB, TC | Valid |
| 2804:5f6c:2000::/35 | TC | Valid |
| 2804:5f6c:4000::/35 | TC | Valid |
| 2804:5f6c:6000::/35 | TC | Valid |
| 2804:5f6c:a000::/35 | TC | Valid |
| 2804:5f6c:c000::/35 | TC | Valid |
| 2804:5f6c:e000::/35 | TC | 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.