Autonomous system
AS44284 TRONIC-AS
Unclassified RIPE
Summary
P.H.U TRONIC
isp residential poland small
TRONIC-AS is operated by P.H.U TRONIC.
What it's used for
- The address space carries residential or small-business access traffic, evidenced by reverse DNS entries such as
host198.128.tronic.plandhost162-128.tronic.pl. - The AS announces 1280 IPv4 addresses across 3 prefixes and maintains 2 observed neighbours, a ratio indicative of a small access provider rather than a transit carrier.
- Traffic consists of end-user connectivity for subscribers in the Radom region of Poland.
Notable
- Registrants for the two /23 prefixes are listed as P.H.U TRONIC with the netname
PL-TRONIC, while the /24 prefix is registered to ABUSE EXATEL with the netnameTRONIC-NET. - The inventory is composed of three distinct IPv4 blocks located entirely in Poland.
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-31, licensed CC BY-NC-SA 3.0. Transit is inferred from observed BGP paths, never declared by either party.
Address space
Summary
IPv4 3 prefixes · 1.28K addresses IPv6 0 prefixes
| Country | Name | Prefixes |
|---|---|---|
| PL | Poland | 3 |
Registry
Allocation record
- Registry
- RIPE
- Handle
AS44284- Registry name
- TRONIC-AS
- Registrant
- P.H.U TRONIC
- Abuse contact
- abuse@tronic.pl
- Registered
- 2007-12-17
- Last changed
- 2018-10-25
- Allocation
- allocated
Declared
PeeringDB profile
- Name
- TRONIC
- 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
- 13% valid · 1 valid, 7 with no ROA
- ROAs
- 1 authorising AS44284
- ASPA
- no ASPA record
- IRR
- 100% registered · 8 of 8 announcements
- Route objects
- 3 naming AS44284
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: 447 networks and 1,845 prefixes, as published 2026-10-31. 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