Network · data from 2026-11-12
AS198990 Pine Hosting
Registry name: PINEHOST-NET Pine Hosting LTD, GB · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS198990, 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.
| 156.236.84.0/24 | Invalid: origin | RIR databaseAFRINIC | 3 0%low visibility |
| 89.28.237.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 89.213.214.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 66.51.96.0/22 | Valid | RIR databaseRIPE | 669 99% |
AS-SET
AS198990'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 1 are in fix.csv.
- ROA: origin1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 156.236.84.0/24 | ROAs covering it name AS17561, not AS198990. If AS198990 should announce it, add a ROA for AS198990. |
Route objects not announced
Every route object with origin AS198990 is announced.
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.