Autonomous system
AS16725 PHILLYIX-CACHES
Hosting ARIN Network Services
Summary
Philadelphia Internet Exchange
infrastructure hosting telecom
The handle and the netname are the same string, and neither one names the exchange.
What it's used for
- An exchange point's own block. One IPv4 prefix and one IPv6 prefix announced from the United States, two hundred and fifty-six addresses, through one observed BGP neighbour.
Notable
- The AS handle is a run-together city nickname, two letters for an exchange, and the word for stored copies of content.
- The single block carries that identical string as its netname, and is registered to the holder's full three-word name.
- So the handle and the netname agree exactly, which is rare, and both describe what the space is for rather than who holds it.
- Three addresses were queried for reverse DNS and none returned a name.
- One observed neighbour carries both the address block and the sixth-version prefix.
Interesting
- An exchange point is a room where other networks meet, and most of its addresses are handed to those networks rather than used by the exchange. A separate autonomous system with one small block is the part the exchange keeps for itself.
- Naming that block for content caches says what sits in the room: providers place copies of popular content at an exchange so local traffic never leaves the city.
- One neighbour is what you expect here. The exchange is not selling transit; it needs a single path out for the few things that must reach the wider network.
This description is AI-generated, best-effort context — not authoritative, and provided without any guarantee of accuracy. Source, and how to suggest an edit.
Interconnection
Peering at a glance
Internet exchanges
No exchange port on file. Many exchanges publish no participant list, so this is not proof of absence.
Transit providers
1 upstream, 0 downstream and 2 adjacent networks observed; most-used upstreams first.
| AS | Network | Paths seen |
|---|---|---|
| AS27228 | Philadelphia Internet Exchange | 102 |
Exchange presence is recorded rather than inferred: the directory collected by Packet Clearing House (https://www.pch.net/ixp/data) on 2026-10-25, licensed CC BY-NC-SA 3.0. Transit is inferred from observed BGP paths, never declared by either party.
Address space
Summary
IPv4 1 prefixes · 256 addresses IPv6 1 prefixes
| Country | Name | Prefixes |
|---|---|---|
| US | United States of America | 2 |
Registry
Allocation record
- Registry
- ARIN
- Handle
AS16725- Registry name
- PHILLYIX-CACHES
- Registrant
- Philadelphia Internet Exchange
- Abuse contact
- admin@phillyix.net
- Registered
- 2023-06-27
- Last changed
- 2023-06-27
- Allocation
- assigned
Declared
PeeringDB profile
- Name
- PhillyIX Cache Network
- Also known as
- PhillyIX CacheNet
- Network type
- Network Services
- Scope
- Not Disclosed
- Traffic ratio
- Not Disclosed
- Peering policy
- Open
- IRR as-set
AS16725:AS-ALL- Present at
- 1 exchanges
- Facilities
- 3 facilities
- Website
- https://phillyix.net/services/caches
PeeringDB records are maintained by the network operator and are not independently verified. Treat them as a statement of intent rather than of fact. For the observed and recorded view, see peering, which lists the exchanges Packet Clearing House has a port on file for.
Routing security
RPKI and IRR
- RPKI
- 100% valid · 2 valid, 0 with no ROA
- ROAs
- 2 authorising AS16725
- ASPA
- no ASPA record
- IRR
- 100% registered · 2 of 2 announcements
- Route objects
- 2 naming AS16725
Reputation
Classification and threat
Hosting Datacenter or cloud provider. Addresses are servers, not people.
Spamhaus DROP
Not on ASN-DROP The network as a whole is not listed.
No DROP prefixes None of its announced space is on the DROP prefix list.
Spamhaus DROP ("Don't Route Or Peer") lists space and networks run by, or hijacked for, spam and cybercrime operations: 443 networks and 1,779 prefixes, as published 2026-10-24. A short, high-confidence list, so a match is worth taking seriously, and absence from it says little on its own.
FBI IC3
No IC3 indicators Nothing from the FBI IC3 feed.
IC3 threat data is alpha. Absence of an indicator is not evidence of good behaviour, only of absence from this one feed.
Elsewhere