Network · data from 2026-11-12

AS18615 Mainstream Fiber Networks

Registry name: MAINSTREAM-FIBER - Mainstream Fiber Networks, LLC, US · PeeringDB

8IPv4 routes 75.0% RPKI valid · 100.0% with a route object

1IPv6 routes 100.0% RPKI valid · 100.0% with a route object

0RPKI invalid 0 origin · 0 maxLength

2No ROA 0 with no route object for this origin

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

0Route objects not announced registered with origin AS18615, seen from no peer

Announced routes

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


38.2.0.0/19	No ROA	Other IRR onlyRADB	673 100%	68
38.194.0.0/18	No ROA	Other IRR onlyRADB	673 100%	68
23.252.0.0/20	Valid	RIR databaseARIN, RADB	673 100%	68
74.116.20.0/22	Valid	RIR databaseARIN, RADB	673 100%	68
147.160.8.0/21	Valid	RIR databaseARIN, RADB	673 100%	68
149.20.248.0/21	Valid	RIR databaseARIN, RADB	673 100%	68
163.182.176.0/20	Valid	RIR databaseARIN, RADB	673 100%	68
206.126.242.0/23	Valid	RIR databaseARIN, RADB	673 100%	68
2607:1c80::/32	Valid	RIR databaseARIN, RADB	634 100%	69

AS-SET

PeeringDB's irr_as_set for AS18615: ARIN::AS18615: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 (AS18615 isn't in the set, or no route object for AS18615 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	AS18615 in it	Not covered
ARIN::AS18615:AS-ALL	ARIN	3	2	16	Yes	0

Name

Database

ASNs

Sets

Route objects

AS18615 in it

Not covered

ARIN::AS18615:AS-ALL

ARIN

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 4 are in fix.csv.

ROA: none2
Route object: RIR2

Change	Prefix or set	Detail	Full-table peers
ROA: none	38.2.0.0/19	No ROA covers it. Add a ROA for AS18615, maxLength 19.	673 of 673
Route object: RIR	38.2.0.0/19	Route object only in RADB. Add it in the RIR database for the space.	673 of 673
ROA: none	38.194.0.0/18	No ROA covers it. Add a ROA for AS18615, maxLength 18.	673 of 673
Route object: RIR	38.194.0.0/18	Route object only in RADB. Add it in the RIR database for the space.	673 of 673

Change

Prefix or set

Detail

Full-table peers

ROA: none

38.2.0.0/19

No ROA covers it. Add a ROA for AS18615, maxLength 19.

673 of 673

Route object: RIR

38.2.0.0/19

Route object only in RADB. Add it in the RIR database for the space.

673 of 673

ROA: none

38.194.0.0/18

No ROA covers it. Add a ROA for AS18615, maxLength 18.

673 of 673

Route object: RIR

38.194.0.0/18

Route object only in RADB. Add it in the RIR database for the space.

673 of 673

Route objects not announced

Every route object with origin AS18615 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.