Autonomous system
AS196858 BETASOFT-AS
Unclassified RIPE
Summary
Betasoft
business poland regional
BETASOFT-AS is operated by Betasoft Sp. z o.o.
What it's used for
- The address space carries corporate infrastructure, evidenced by the netname
Betasoftand reverse DNS entrygate.bnet.pl. - The AS announces 2048 IPv4 addresses across 1 prefix and 1 IPv6 prefix, with 5 observed neighbours, indicating a small-scale business network rather than a transit or large access provider.
- Traffic from this AS consists of internal corporate endpoints and services for Betasoft Sp. z o.o., a Polish company.
Notable
- Registrants align with the announcer, listing
BETASOFT Network TeamandBetasoft Sp. z o.o.for the primary prefix. - The inventory consists of a single contiguous IPv4 block (213.5.200.0/21) and one IPv6 /48, representing a compact, self-contained corporate estate.
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
Recorded at 1 exchange in 1 country, largest first.
| Exchange | Location | Their address |
|---|---|---|
| Thinx IX | Warsaw, Poland | 212.91.1.89 |
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 1 prefixes · 2.05K addresses IPv6 1 prefixes
| Country | Name | Prefixes |
|---|---|---|
| PL | Poland | 2 |
Registry
Allocation record
- Registry
- RIPE
- Handle
AS196858- Registry name
- BETASOFT-AS
- Registrant
- ATMAN-MNT
- Abuse contact
- abuse@betasoft.pl
- Registered
- 2009-11-27
- Last changed
- 2022-05-06
- Allocation
- allocated
Declared
PeeringDB profile
- Name
- Betasoft
- Scope
- Regional
- Traffic ratio
- Balanced
- Peering policy
- Open
- Present at
- 2 exchanges
- Website
- http://betasoft.pl
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 AS196858
- ASPA
- no ASPA record
- IRR
- 100% registered · 2 of 2 announcements
- Route objects
- 3 naming AS196858
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