Network · data from 2026-11-12
AS18886 InLine Connections
Registry name: INLINE-NET - Uniti Fiber Holdings Inc., US · PeeringDB
11IPv4 routes
0.0% RPKI valid · 90.9% with a route object
0IPv6 routes
1RPKI invalid
1 origin · 0 maxLength
10No ROA
1 with no route object for this origin
1Low visibility
seen by under 10% of full-table peers
30Route objects not announced
registered with origin AS18886, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS18886, 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.
| 216.170.82.0/24 | Invalid: origin | Nonecovered by 216.170.64.0/19 | 61 9%low visibility |
| 216.170.64.0/19 | No ROA | Other IRR onlyNTTCOM, RADB | 665 99% |
| 216.170.69.0/24 | No ROA | Other IRR onlyNTTCOM | 663 99% |
| 216.170.70.0/23 | No ROA | Other IRR onlyNTTCOM | 663 99% |
| 216.170.72.0/22 | No ROA | Other IRR onlyNTTCOM | 663 99% |
| 216.170.76.0/23 | No ROA | Other IRR onlyRADB | 663 99% |
| 216.170.78.0/24 | No ROA | Other IRR onlyNTTCOM | 663 99% |
| 216.170.80.0/24 | No ROA | Other IRR onlyNTTCOM | 663 99% |
| 216.170.81.0/24 | No ROA | Other IRR onlyNTTCOM | 663 99% |
| 216.170.89.0/24 | No ROA | Other IRR onlyNTTCOM | 663 99% |
| 216.170.90.0/23 | No ROA | Other IRR onlyNTTCOM | 663 99% |
AS-SET
AS18886'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 52 are in fix.csv.
- ROA: origin1
- ROA: none10
- Route object: none1
- Route object: RIR10
- Route object: not announced30
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 216.170.82.0/24 | ROAs covering it name AS13760, not AS18886. If AS18886 should announce it, add a ROA for AS18886. |
| Route object: none | 216.170.82.0/24 | No route object for it. A route object for 216.170.64.0/19 with origin AS18886 covers it (filters allowing more-specifics accept it). Add a route object with origin AS18886 in the RIR database for the space. |
| ROA: none | 216.170.64.0/19 | No ROA covers it. Add a ROA for AS18886, maxLength 19. |
| Route object: RIR | 216.170.64.0/19 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 216.170.69.0/24 | No ROA covers it. Add a ROA for AS18886, maxLength 24. |
| Route object: RIR | 216.170.69.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| ROA: none | 216.170.70.0/23 | No ROA covers it. Add a ROA for AS18886, maxLength 23. |
| Route object: RIR | 216.170.70.0/23 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| ROA: none | 216.170.72.0/22 | No ROA covers it. Add a ROA for AS18886, maxLength 22. |
| Route object: RIR | 216.170.72.0/22 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| ROA: none | 216.170.76.0/23 | No ROA covers it. Add a ROA for AS18886, maxLength 23. |
| Route object: RIR | 216.170.76.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 216.170.78.0/24 | No ROA covers it. Add a ROA for AS18886, maxLength 24. |
| Route object: RIR | 216.170.78.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| ROA: none | 216.170.80.0/24 | No ROA covers it. Add a ROA for AS18886, maxLength 24. |
| Route object: RIR | 216.170.80.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| ROA: none | 216.170.81.0/24 | No ROA covers it. Add a ROA for AS18886, maxLength 24. |
| Route object: RIR | 216.170.81.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| ROA: none | 216.170.89.0/24 | No ROA covers it. Add a ROA for AS18886, maxLength 24. |
| Route object: RIR | 216.170.89.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| ROA: none | 216.170.90.0/23 | No ROA covers it. Add a ROA for AS18886, maxLength 23. |
| Route object: RIR | 216.170.90.0/23 | Route object only in NTTCOM. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS18886 whose prefix no peer sees AS18886 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 216.170.64.0/22 | NTTCOM, RADB | No ROA |
| 216.170.64.0/24 | NTTCOM | No ROA |
| 216.170.65.0/24 | NTTCOM | No ROA |
| 216.170.66.0/24 | NTTCOM | No ROA |
| 216.170.67.0/24 | NTTCOM | No ROA |
| 216.170.68.0/24 | NTTCOM | No ROA |
| 216.170.70.0/24 | NTTCOM | No ROA |
| 216.170.71.0/24 | NTTCOM | No ROA |
| 216.170.72.0/24 | NTTCOM | No ROA |
| 216.170.73.0/24 | NTTCOM | No ROA |
| 216.170.74.0/24 | NTTCOM | No ROA |
| 216.170.75.0/24 | NTTCOM | No ROA |
| 216.170.76.0/22 | NTTCOM | No ROA |
| 216.170.76.0/24 | NTTCOM | No ROA |
| 216.170.77.0/24 | NTTCOM | No ROA |
| 216.170.80.0/23 | NTTCOM | No ROA |
| 216.170.84.0/22 | NTTCOM | No ROA |
| 216.170.86.0/24 | NTTCOM | No ROA |
| 216.170.87.0/24 | NTTCOM | No ROA |
| 216.170.88.0/23 | NTTCOM | No ROA |
| 216.170.88.0/24 | NTTCOM | No ROA |
| 216.170.90.0/24 | NTTCOM | No ROA |
| 216.170.91.0/24 | NTTCOM | No ROA |
| 216.170.92.0/22 | NTTCOM, RADB | No ROA |
| 216.170.92.0/23 | NTTCOM | No ROA |
| 216.170.92.0/24 | NTTCOM | No ROA |
| 216.170.93.0/24 | NTTCOM | No ROA |
| 216.170.94.0/23 | NTTCOM | No ROA |
| 216.170.94.0/24 | NTTCOM | No ROA |
| 216.170.95.0/24 | NTTCOM | 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.