Network · data from 2026-11-12

AS14333 On-Ramp Indiana, Inc.

Registry name: ORI-NET - On-Ramp Indiana, Inc. (ORI.NET), US · PeeringDB

5IPv4 routes 100.0% RPKI valid · 100.0% with a route object

3IPv6 routes 100.0% RPKI valid · 33.3% with a route object

0RPKI invalid 0 origin · 0 maxLength

0No ROA 2 with no route object for this origin

0Low visibility seen by under 10% of full-table peers

1Route objects not announced registered with origin AS14333, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS14333, 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.


2602:ff99:2::/47	Valid	Nonecovered by 2602:ff99::/32	605 95%	68
2602:ff99:5::/48	Valid	Nonecovered by 2602:ff99::/32	605 95%	67
208.72.104.0/21	Valid	RIR databaseARIN	670 100%	68
158.51.48.0/23	Valid	RIR databaseARIN	668 99%	68
192.73.220.0/24	Valid	RIR databaseARIN	668 99%	68
199.168.128.0/22	Valid	RIR databaseARIN	668 99%	68
206.168.136.0/22	Valid	RIR databaseARIN	668 99%	68
2602:f793:1::/48	Valid	RIR databaseARIN	605 95%	67

AS-SET

PeeringDB's irr_as_set for AS14333: ARIN::AS14333:AS-ALL. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS14333 isn't in the set, or no route object for AS14333 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

Name	Database	ASNs	Sets	Route objects	AS14333 in it	Not covered
ARIN::AS14333:AS-ALL	ARIN	22	4	6,280	Yes	0

Name

Database

ASNs

Sets

Route objects

AS14333 in it

Not covered

ARIN::AS14333:AS-ALL

ARIN

6,280

Yes

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.

Route object: none2
Route object: not announced1

Change	Prefix or set	Detail	Full-table peers
Route object: none	2602:ff99:2::/47	No route object for it. A route object for 2602:ff99::/32 with origin AS14333 covers it (filters allowing more-specifics accept it). Add a route object with origin AS14333 in the RIR database for the space.	605 of 636
Route object: none	2602:ff99:5::/48	No route object for it. A route object for 2602:ff99::/32 with origin AS14333 covers it (filters allowing more-specifics accept it). Add a route object with origin AS14333 in the RIR database for the space.	605 of 636

Change

Prefix or set

Detail

Full-table peers

Route object: none

2602:ff99:2::/47

No route object for it. A route object for 2602:ff99::/32 with origin AS14333 covers it (filters allowing more-specifics accept it). Add a route object with origin AS14333 in the RIR database for the space.

605 of 636

Route object: none

2602:ff99:5::/48

605 of 636

Route objects not announced

Route objects with origin AS14333 whose prefix no peer sees AS14333 announce. Many are kept on purpose (backup routes, space announced only in some places).


2602:ff99::/32	ARIN	Valid

2602:ff99::/32

ARIN

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.