Network · data from 2026-11-12

AS63154 DCCC

Registry name: DCCC - Delaware County Community College, US · PeeringDB

3IPv4 routes 100.0% RPKI valid · 66.7% with a route object

5IPv6 routes 100.0% RPKI valid · 20.0% with a route object

0RPKI invalid 0 origin · 0 maxLength

0No ROA 5 with no route object for this origin

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

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

Announced routes

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


104.218.42.0/24	Valid	Nonecovered by 104.218.40.0/22	673 100%	67
2620:11d:2000::/42	Valid	Nonecovered by 2620:11d:2000::/40	605 95%	67
2620:11d:2040::/42	Valid	Nonecovered by 2620:11d:2000::/40	605 95%	67
2620:11d:2080::/42	Valid	Nonecovered by 2620:11d:2000::/40	605 95%	67
2620:11d:20c0::/42	Valid	Nonecovered by 2620:11d:2000::/40	605 95%	67
104.218.41.0/24	Valid	Other IRR onlyRADB	671 100%	68
104.218.40.0/22	Valid	RIR databaseARIN	671 100%	68
2620:11d:2000::/40	Valid	RIR databaseARIN, RADB	605 95%	67

AS-SET

AS63154'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 6 are in fix.csv.

Route object: none5
Route object: RIR1

Change	Prefix or set	Detail	Full-table peers
Route object: none	104.218.42.0/24	No route object for it. A route object for 104.218.40.0/22 with origin AS63154 covers it (filters allowing more-specifics accept it). Add a route object with origin AS63154 in the RIR database for the space.	673 of 673
Route object: none	2620:11d:2000::/42	No route object for it. A route object for 2620:11d:2000::/40 with origin AS63154 covers it (filters allowing more-specifics accept it). Add a route object with origin AS63154 in the RIR database for the space.	605 of 636
Route object: none	2620:11d:2040::/42	No route object for it. A route object for 2620:11d:2000::/40 with origin AS63154 covers it (filters allowing more-specifics accept it). Add a route object with origin AS63154 in the RIR database for the space.	605 of 636
Route object: none	2620:11d:2080::/42	No route object for it. A route object for 2620:11d:2000::/40 with origin AS63154 covers it (filters allowing more-specifics accept it). Add a route object with origin AS63154 in the RIR database for the space.	605 of 636
Route object: none	2620:11d:20c0::/42	No route object for it. A route object for 2620:11d:2000::/40 with origin AS63154 covers it (filters allowing more-specifics accept it). Add a route object with origin AS63154 in the RIR database for the space.	605 of 636
Route object: RIR	104.218.41.0/24	Route object only in RADB. Add it in the RIR database for the space.	671 of 673

Change

Prefix or set

Detail

Full-table peers

Route object: none

104.218.42.0/24

No route object for it. A route object for 104.218.40.0/22 with origin AS63154 covers it (filters allowing more-specifics accept it). Add a route object with origin AS63154 in the RIR database for the space.

673 of 673

Route object: none

2620:11d:2000::/42

No route object for it. A route object for 2620:11d:2000::/40 with origin AS63154 covers it (filters allowing more-specifics accept it). Add a route object with origin AS63154 in the RIR database for the space.

605 of 636

Route object: none

2620:11d:2040::/42

605 of 636

Route object: none

2620:11d:2080::/42

605 of 636

Route object: none

2620:11d:20c0::/42

605 of 636

Route object: RIR

104.218.41.0/24

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

671 of 673

Route objects not announced

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