Autonomous system
AS24631 FANAPTELECOM-FCP
Unclassified RIPE
Summary
Fanap Telecom
residential isp iran access
FANAPTELECOM-FCP is operated by Fanap Telecom (Tose'h Fanavari Ertebabat Pasargad Arian Co. PJS).
What it's used for
- The address space carries residential and business customer traffic, evidenced by netnames such as
FanapTelecom-USERS,FANAPTELECOM-CUSTOMERS, andFANAPTELECOM-NETWORK. - Reverse DNS entries consistently point to
int0.client.access.fanaptelecom.net, confirming the space is used for end-user access. - With 105,216 IPv4 addresses announced across 179 prefixes and only 27 observed neighbours, the high address-to-neighbour ratio indicates an access/eyeball network rather than a transit provider.
Notable
- Registrants are consistent with the announcer, primarily listing
FANAPTELECOM NETWORKandTose'h Fanavari Ertebabat Pasargad Arian Co. PJS. - The address inventory is finely subdivided into numerous /21 and /22 blocks, typical of a large domestic ISP managing distinct customer pools.
- Some prefixes carry legacy netnames like
IR-JAVIDAN, suggesting historical acquisitions or rebranding within the operator's portfolio.
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-19, licensed CC BY-NC-SA 3.0. Transit is inferred from observed BGP paths, never declared by either party.
Address space
Summary
IPv4 187 prefixes · 112K addresses IPv6 1 prefixes
| Country | Name | Prefixes |
|---|---|---|
| IR | Iran (Islamic Republic of) | 188 |
Registry
Allocation record
- Registry
- RIPE
- Handle
AS24631- Registry name
- FANAPTELECOM-FCP
- Registrant
- ir-javidan-1-mnt
- Abuse contact
- abuse@fanaptelecom.ir
- Registered
- 2002-06-28
- Last changed
- 2026-08-08
- Allocation
- allocated
Declared
PeeringDB profile
- Name
- Tose'h Fanavari Ertebabat Pasargad Arian Co. PJS
- Scope
- Not Disclosed
- Traffic ratio
- Not Disclosed
- Peering policy
- Open
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 · 213 valid, 0 with no ROA
- ROAs
- 239 authorising AS24631
- ASPA
- no ASPA record
- IRR
- 99% registered · 210 of 213 announcements 3 other origin
- Route objects
- 421 naming AS24631
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,783 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