Autonomous system
AS60653 FEEDLY-DEVHD
Unclassified RIPE Enterprise
Summary
Feedly
business saas rss enterprise
FEEDLY-DEVHD is operated by Feedly, Inc.
What it's used for
- The address space carries corporate infrastructure, evidenced by the netname
FEEDLY-NYCon 206.41.73.0/24 and the registrantFeedly. - The AS announces 512 IPv4 addresses across 2 prefixes and maintains 4 observed neighbours, a ratio consistent with a small-scale enterprise network rather than a transit or access provider.
- Traffic from this AS consists of web and API endpoints for Feedly’s RSS reader and content aggregation services, supporting its SaaS business model.
Notable
- Registrants align with the announcer for the 206.41.73.0/24 prefix, while the 8.29.198.0/24 prefix is registered to
BSO NETWORK INCwith netnameLVLT-BN-5-8-29-192, indicating leased or legacy space. - The address inventory is small and fragmented, consisting of two /24 blocks, one of which is associated with Level 3 Communications history via the
LVLTnetname.
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.
Exchange presence is recorded rather than inferred: the directory collected by Packet Clearing House (https://www.pch.net/ixp/data) on 2026-10-20, licensed CC BY-NC-SA 3.0. Transit is inferred from observed BGP paths, never declared by either party.
Address space
Summary
IPv4 2 prefixes · 512 addresses IPv6 0 prefixes
| Country | Name | Prefixes |
|---|---|---|
| US | United States of America | 2 |
Registry
Allocation record
- Registry
- RIPE
- Handle
AS60653- Registry name
- FEEDLY-DEVHD
- Registrant
- BSOCOM-MNT
- Abuse contact
- abuse@bsonetwork.com
- Registered
- 2013-06-04
- Last changed
- 2020-06-16
- Allocation
- allocated
Declared
PeeringDB profile
- Name
- FEEDLY-DEVHD
- Also known as
- Feedly
- Network type
- Enterprise
- Scope
- Not Disclosed
- Traffic ratio
- Not Disclosed
- Peering policy
- Open
- IRR as-set
AS60653:AS-ALL- Facilities
- 2 facilities
- Website
- https://www.feedly.com
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
- 0% valid · 0 valid, 2 with no ROA
- ROAs
- 0 authorising AS60653
- ASPA
- no ASPA record
- IRR
- 100% registered · 2 of 2 announcements
- Route objects
- 3 naming AS60653
Reputation
Classification and threat
Unclassified Not in the curated lists. Most of the ~80,000 allocated ASNs are not.
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: 442 networks and 1,778 prefixes, as published 2026-10-20. 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