Autonomous system
AS219359 EDGE-AS Edge Core FZE
Unclassified RIPE Content
Summary
Edge Core FZE
hosting datacenter uae
The AS handle EDGE-AS is held by Edge Core FZE.
What it's used for
- The address space carries data center infrastructure, with netnames
EDGE-CORE-NETandAM-VERNON-*registered to Edge Core FZE and Vernon LLC respectively. - The AS announces 3840 IPv4 addresses across 10 prefixes and 1 IPv6 prefix, with 4 observed neighbours, indicating a hosting or content delivery role rather than transit.
- Traffic from this AS consists of web and API endpoints hosted in Edge Core's global network of data centers.
Notable
- Registrants are split between Edge Core FZE (netname
EDGE-CORE-NET) and Vernon LLC (netnamesAM-VERNON-*), suggesting leased or acquired address space. - The address inventory is fragmented across multiple /24 and /23 blocks in different ranges (157.228.0.0/16, 132.243.0.0/16, 45.86.0.0/16, 185.113.0.0/16).
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-06, licensed CC BY-NC-SA 3.0. Transit is inferred from observed BGP paths, never declared by either party.
Address space
Summary
IPv4 11 prefixes · 4.10K addresses IPv6 1 prefixes
| Country | Name | Prefixes |
|---|---|---|
| AE | United Arab Emirates | 12 |
Registry
Allocation record
- Registry
- RIPE
- Handle
AS219359- Registry name
- EDGE-AS
- Registrant
- EDGE-CORE-MNT
- Abuse contact
- abuse@edge-core.net
- Registered
- 2026-06-24
- Last changed
- 2026-08-22
- Allocation
- allocated
Declared
PeeringDB profile
- Name
- Edge Core FZE
- Network type
- Content
- Scope
- Global
- Traffic ratio
- Balanced
- Peering policy
- Open
- Website
- https://edge-core.net
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
- 94% valid · 16 valid, 0 with no ROA 1 RPKI-invalid
- ROAs
- 11 authorising AS219359
- ASPA
- no ASPA record
- IRR
- 94% registered · 16 of 17 announcements
- Route objects
- 18 naming AS219359
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,854 prefixes, as published 2026-11-06. 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