Network · data from 2026-11-12
AS199735 Inclusive-Bytes-CIC Inclusive Bytes C.I.C
Registry name: Inclusive-Bytes-CIC Inclusive Bytes C.I.C, GB · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS199735, 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.
| 96.62.127.0/24 | Invalid: origin | Other origin only | 2 0%low visibility |
| 2a06:9801:22b::/48 | No ROA | RIR databaseRIPE | 1 0%low visibility |
| 2a13:9500:38::/48 | Valid | RIR databaseRIPE | 1 0%low visibility |
AS-SET
AS199735 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 3 are in fix.csv.
- ROA: origin1
- ROA: none1
- Route object: none1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 96.62.127.0/24 | ROAs covering it name AS834, not AS199735. If AS199735 should announce it, add a ROA for AS199735. |
| Route object: none | 96.62.127.0/24 | Route objects for it name AS834. Add a route object with origin AS199735 in the RIR database for the space. |
| ROA: none | 2a06:9801:22b::/48 | No ROA covers it. Add a ROA for AS199735, maxLength 48. |
Route objects not announced
Every route object with origin AS199735 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.