bgpreport

Network · data from 2026-11-12

AS22638 PHILORCH-ASN - The Philadelphia Orchestra Association

Registry name: PHILORCH-ASN - The Philadelphia Orchestra Association, US · not in PeeringDB

1IPv4 routes 0.0% RPKI valid · 0.0% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
1No ROA 1 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
16Route objects not announced registered with origin AS22638, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS22638, 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.
204.75.178.0/24 No ROA Other origin only 673 100% 67

AS-SET

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

  • ROA: none1
  • Route object: none1
  • Route object: not announced16
ChangePrefix or setDetailFull-table peers
ROA: none204.75.178.0/24No ROA covers it. Add a ROA for AS22638, maxLength 24.673 of 673
Route object: none204.75.178.0/24Route objects for it name AS6372, AS7029. Add a route object with origin AS22638 in the RIR database for the space.673 of 673

Route objects not announced

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

199.60.62.0/24RADBNo ROA
199.60.96.0/24RADBNo ROA
199.60.107.0/24RADBNo ROA
199.60.118.0/24RADBNo ROA
199.60.222.0/24RADBNo ROA
199.175.4.0/24RADBNo ROA
204.174.113.0/24RADBNo ROA
204.174.116.0/24RADBNo ROA
204.174.117.0/24RADBNo ROA
204.174.230.0/24RADBNo ROA
204.239.19.0/24RADBNo ROA
204.239.207.0/24RADBNo ROA
204.239.208.0/24RADBNo ROA
204.239.216.0/24RADBNo ROA
204.239.240.0/24RADBNo ROA
204.239.242.0/24RADBNo 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.