Autonomous system
AS56388 AMBER-AS Amberway Development LTD
Unclassified RIPE
Summary
Amberway Development LTD
business belize small
The AS handle AMBER-AS is held by Amberway Development LTD.
What it's used for
- The space carries business traffic for a Belize-based development company, identified by the netname
BZ-AMBERWAY-20160620and registrantAmberway Development LTD. - The network announces a single IPv4 prefix,
185.156.200.0/22, comprising 1024 addresses, and maintains 19 observed neighbours. - Traffic from this AS consists of corporate office workers and web/API endpoints associated with the company's operations in Belize City.
Notable
- The RDAP registrant
Amberway Development LTDmatches the registry holder and the AS nameAMBER-AS. - The address inventory consists of a single contiguous /22 block, indicating a small, self-contained corporate estate rather than a multi-site or access network.
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-11-07, 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 · 1.02K addresses IPv6 0 prefixes
| Country | Name | Prefixes |
|---|---|---|
| BZ | Belize | 1 |
Registry
Allocation record
- Registry
- RIPE
- Handle
AS56388- Registry name
- AMBER-AS
- Registrant
- AMBER-MNT
- Abuse contact
- abuse@amberway.bz
- Registered
- 2016-06-20
- Last changed
- 2022-02-02
- Allocation
- allocated
Declared
PeeringDB profile
- Name
- Amberway Development LTD
- Scope
- Not Disclosed
- Traffic ratio
- Not Disclosed
- Peering policy
- Open
- Present at
- 3 exchanges
- Facilities
- 2 facilities
- Website
- http://amberway.bz
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 · 4 valid, 0 with no ROA
- ROAs
- 4 authorising AS56388
- ASPA
- no ASPA record
- IRR
- 100% registered · 4 of 4 announcements
- Route objects
- 7 naming AS56388
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: 454 networks and 1,852 prefixes, as published 2026-11-08. 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