Autonomous system
AS52355 Jalasoft Corp.
Unclassified APNIC
Summary
Jalasoft
business bolivia software
AS52355 is held by Jalasoft Corp.
What it's used for
- The space carries corporate infrastructure for Jalasoft, a software development and IT services company, as indicated by the registrant
Jalasoft Corp.and netname200.106.244.0 - 200.106.245.255. - The AS announces 512 IPv4 addresses across 1 prefix (
200.106.244.0/23) with 2 observed neighbours, a ratio consistent with an internal corporate estate rather than a transit or access network. - Traffic from this AS consists of office workers and web/API endpoints for Jalasoft's business operations.
Notable
- The RDAP registrant
Jalasoft Corp.matches the AS holder, confirming consistent ownership of the address space. - The address inventory consists of a single contiguous /23 block, typical of a corporate allocation for internal use.
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-27, 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 · 512 addresses IPv6 0 prefixes
| Country | Name | Prefixes |
|---|---|---|
| BO | Bolivia | 1 |
Registry
Allocation record
- Registry
- APNIC
- Handle
AS52355- Registry name
- 52355
- Registrant
- Jalasoft Corp.
- Abuse contact
- gustavo.peredo@jalasoft.com
- Registered
- 2011-12-06
- Last changed
- 2011-12-06
- Allocation
- allocated
Declared
PeeringDB profile
- Name
- Jalasoft
- Scope
- Not Disclosed
- Traffic ratio
- Not Disclosed
- Peering policy
- Open
- Website
- http://www.jalasoft.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 AS52355
- ASPA
- no ASPA record
- IRR
- 100% registered · 2 of 2 announcements
- Route objects
- 1 naming AS52355
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,852 prefixes, as published 2026-10-27. 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