Autonomous system
AS207500 MARTCOM-AS
Unclassified RIPE
Summary
Martcom
business poland small
MARTCOM-AS is operated by Mirela Bugdol trading as FHU Martcom.
What it's used for
- The address space is registered under the netname
PL-MARTCOM2-20191107with registrantMARTCOM DBM; Mirela Bugdol trading as FHU Martcom. - The AS announces 1024 IPv4 addresses across 2 prefixes and maintains 4 observed neighbours, indicating a small-scale business or local access network rather than a transit provider.
- Traffic from this AS consists of local business or residential services provided by Martcom in the Krzyżanowice area of Poland.
Notable
- Registrants for both announced prefixes (
195.254.142.0/23and195.254.154.0/23) align with the AS holder, identifying the operator as Mirela Bugdol trading as FHU Martcom. - The inventory consists of two contiguous /23 blocks in the 195.254.0.0/16 range, typical of a small Polish ISP or local service provider.
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-30, 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 · 1.02K addresses IPv6 0 prefixes
| Country | Name | Prefixes |
|---|---|---|
| PL | Poland | 2 |
Registry
Allocation record
- Registry
- RIPE
- Handle
AS207500- Registry name
- MARTCOM-AS
- Registrant
- lir-pl-martcom2-1-MNT
- Abuse contact
- info@martcom.pl
- Registered
- 2020-01-22
- Last changed
- 2021-12-30
- Allocation
- allocated
Declared
PeeringDB profile
- Name
- Martcom
- 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
- 0% valid · 0 valid, 2 with no ROA
- ROAs
- 0 authorising AS207500
- ASPA
- no ASPA record
- IRR
- 100% registered · 2 of 2 announcements
- Route objects
- 3 naming AS207500
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: 448 networks and 1,849 prefixes, as published 2026-10-30. 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