SYDMAE is a network operating identity for AS212071, visible in RIPE, PeeringDB, and routing mirrors, associated with Sydney Morrison. It presents a modest routing surface: a small content network with selective peering, a geofeed, and upstreams. No verified legal entity, revenue model, or direct CloudExis link is available. The profile's intelligence value lies in monitoring its public routing and registry signals for changes that could affect address-space reachability and geolocation. Evidence is bounded to official records and directory data; live BGP views differ. Key watchpoints: registry modifications, prefix announcements, upstream shifts, geofeed updates, and any new corporate registration.
SYDMAE operates as the publicly visible name for AS212071, through which Sydney Morrison administers a small content-focused autonomous network. Its role encompasses maintaining RIPE registry records, defining BGP import/export policies, publishing PeeringDB interconnection metadata, and providing a geofeed file that can affect IP geolocation systems.
Changes to SYDMAE's AS212071 registry object, route policies, upstream selections, BGP.Exchange presence, or geofeed references can shift reachability and attribution for the associated address space. Network operators, IP intelligence vendors, and geolocation services rely on these public signals when making routing and validation decisions.
Changes to SYDMAE's AS212071 registry object, route policies, upstream selections, BGP.Exchange presence, or geofeed references can shift reachability and attribution for the associated address space. Network operators, IP intelligence vendors, and geolocation services rely on these public signals when making routing and validation decisions.
SYDMAE operates as the publicly visible name for AS212071, through which Sydney Morrison administers a small content-focused autonomous network. Its role encompasses maintaining RIPE registry records, defining BGP import/export policies, publishing PeeringDB interconnection metadata, and providing a geofeed file that can affect IP geolocation systems.
The accuracy of SYDMAE's public records directly impacts the routing and classification of its announced IPv4 prefixes. Inaccurate or stale information could lead to reachability issues, misrouting, or incorrect geolocation, affecting downstream services that depend on the address space, even if the network itself is small.
SYDMAE is a network operating identity for AS212071, visible in RIPE, PeeringDB, and routing mirrors, associated with Sydney Morrison. It presents a modest routing surface: a small content network with selective peering, a geofeed, and upstreams. No verified legal entity, revenue model, or direct CloudExis link is available. The profile's intelligence value lies in monitoring its public routing and registry signals for changes that could affect address-space reachability and geolocation. Evidence is bounded to official records and directory data; live BGP views differ. Key watchpoints: registry modifications, prefix announcements, upstream shifts, geofeed updates, and any new corporate registration.
The accuracy of SYDMAE's public records directly impacts the routing and classification of its announced IPv4 prefixes. Inaccurate or stale information could lead to reachability issues, misrouting, or incorrect geolocation, affecting downstream services that depend on the address space, even if the network itself is small.
| 0.90–1.00 | A | High — direct sources |
| 0.75–0.89 | A/B | Strong |
| 0.55–0.74 | B/C | Medium |
| 0.35–0.54 | C/D | Weak–medium |
| 0.10–0.34 | D | Weak signal |
| 0.00–0.09 | D | Internal monitoring |
Several public sources
SYDMAE
SYDMAE is the public network operating identity for AS212071, a small content-oriented autonomous system associated with Sydney Morrison. It appears in RIPE/RDAP, PeeringDB, and routing mirrors, with selective peering, upstream transit to providers such as The Constant Company, and address space labeled under CloudExis. The entity is not verified as a standalone incorporated company, and its commercial model remains undocumented in public sources.
Why It Matters
The accuracy of SYDMAE's public records directly impacts the routing and classification of its announced IPv4 prefixes. Inaccurate or stale information could lead to reachability issues, misrouting, or incorrect geolocation, affecting downstream services that depend on the address space, even if the network itself is small.
What Public Sources Show
SYDMAE is the public network name for AS212071, a small autonomous system operating out of the United States. It is not a verified company but a bounded operating identity linked in public registry and peering records to an individual named Sydney Morrison.
The network's importance is technical, not commercial: every change in its routing posture can shift how other networks reach its address space and how IP geolocation systems attribute its prefixes.
Registry records at RIPE and routing mirrors like bgp.tools show AS212071 was created in March 2025 and last modified in October 2025. Its RPSL policy defines import and export relationships with upstreams SYSTEM36 and The Constant Company. PeeringDB classifies it as a Content network with selective peering, typical outbound-heavy traffic, and a geofeed file intended to aid location accuracy.
Cloudflare Radar and IPLocate independently list the same identity, while CIDR Report observes a small number of originated IPv4 prefixes and upstream adjacency.
The control surface is entirely public: the aut-num object, AS212071:AS-ALL, PeeringDB entries, BGP.Exchange presence, and the geofeed reference. Any modification to these—whether a registry update, a new prefix announcement, or a withdrawn route—can alter the reachability and trust assessment of the IP space behind SYDMAE. RPKI validation status further affects how routes are scored by security services.
Operational watchpoints include changes to the RIPE aut-num or AS-SET, fluctuations in prefix counts (currently 1–3 IPv4 routes and 0–4 IPv6, depending on the directory), shifts in upstream providers, and the addition or removal of the geofeed. A spike in announced prefixes or the appearance of a formal corporate registration would raise SYDMAE from a curiosity to a network with broader materiality.
Critical gaps remain. No public source confirms SYDMAE as a standalone legal entity; it could be a trading name, a personal project, or a department. There is no verified customer base, billing arrangement, or monetization model. The connection to CloudExis—a Minnesota-based hosting provider that occasionally labels AS212071 prefixes—is inferred from routing data and a Trustpilot reply mentioning Sydney Morrison, but no corporate link is proven.
Sydney Morrison's authority is limited to registry and peering representations; no formal title or employment relationship is independently verifiable.
For network operators, IP intelligence vendors, and geolocation services, SYDMAE represents a small but active signal. Its public records should be monitored for changes that could cascade into reachability or attribution errors. Until a verifiable legal entity or confirmable business model emerges, the profile remains a technical watchpoint, not a corporate assessment.
Operating Surface
SYDMAE operates as the publicly visible name for AS212071, through which Sydney Morrison administers a small content-focused autonomous network. Its role encompasses maintaining RIPE registry records, defining BGP import/export policies, publishing PeeringDB interconnection metadata, and providing a geofeed file that can affect IP geolocation systems.
Changes to SYDMAE's AS212071 registry object, route policies, upstream selections, BGP.Exchange presence, or geofeed references can shift reachability and attribution for the associated address space. Network operators, IP intelligence vendors, and geolocation services rely on these public signals when making routing and validation decisions.
Watchpoints
SYDMAE represents a small but technically consequential autonomous network. Its importance is not scale but the dependency that other networks and IP intelligence systems have on its routing posture. Changes to its registry, BGP, or geofeed can ripple through reachability and geolocation. The operator identity is unclear beyond Sydney Morrison; no corporate structure or commercial model is known.
This makes every public signal—registry update, prefix count fluctuation, upstream addition—a potential watchpoint.
- Modification of AS212071's aut-num or AS-SET in RIPE; 2) substantial change in announced IPv4/IPv6 prefixes; 3) removal or alteration of the geofeed reference; 4) new upstreams or peering; 5) registration of a formal legal entity for SYDMAE or CloudExis; 6) changes in RPKI/ROA state.
No primary source confirms SYDMAE as an incorporated entity. Direct customers, billing, and workload ownership are unverified. The CloudExis relationship is circumstantial from prefix labels and a Trustpilot reply referencing Sydney Morrison, but no contractual or corporate linkage is proven. Formal title or employer authority for Sydney Morrison is absent. Live routing datasets vary on prefix counts.
Sources
- Registry RDAP / WHOIS record - public-source identity and registry context for SYDMAE.
- Registry RDAP / WHOIS record - RDAP/RIPE registry lookup for AS212071 provides the official public registry context for the SYDMAE aut-num and its associated entity records.
- Internet registry record - bgp.tools mirrors RIPE/RPSL data showing aut-num AS212071, as-name SYDMAE, descr Sydney Morrison, sponsoring organization, import/export policies for AS20473, AS23470 and AS59678, status ASSIGNED, created 2025-03-03 and last-modified 2025-10-13.
- PeeringDB network profile - PeeringDB lists AS212071 as SYDMAE, organization Sydney Morrison, also known as SYDMAE, website syd.gg, network type Content, 100-1000 Mbps traffic, mostly outbound traffic ratio, North America geographic scope, selective peering policy and public BGP.Exchange entries.
- radar.cloudflare.com - Cloudflare Radar recognizes AS212071 under the name SYDMAE, places it in the United States and links website syd.gg, adding independent network-directory visibility.
- ipinfo.io - IPinfo identifies AS212071 as Sydney Morrison with website syd.gg, country United States, registry RIPE, ASN type Business and address-range data including CloudExis LLC-labeled ranges.
- cidr-report.org - CIDR Report observes AS212071 as SYDMAE - Sydney Morrison, US, with originated IPv4 address space and upstream adjacency including SYSTEM36 and The Constant Company in its route-collector view.
- Operator website - CloudExis public material describes web hosting, VPS and IP transit services; this is relevant only as associated hosting-infrastructure context because separate routing datasets label some AS212071-visible ranges as CloudExis LLC.
- uk.trustpilot.com - Trustpilot's claimed CloudExis LLC profile describes CloudExis as a Minnesotan cloud provider offering web hosting and VPS services in the United States, and review replies publicly use Sydney Morrison/CloudExis role language.
- iplocate.io - Corroborates AS212071 as Sydney Morrison / SYDMAE, RIPE registry, United States, allocated on 2025-03-03 and updated on 2025-10-13, with CloudExis LLC-labeled IPv4 prefixes and upstreams including AS20473 and AS59678.
- syd.gg - Self-published site linked by PeeringDB and Cloudflare as syd.gg presents Sydney Mae/Sydney Morrison public profile context; useful for operator identity context but not independent verification of formal corporate authority.
- PeeringDB network profile - Operator-maintained peering profile listing SYDMAE, organization Sydney Morrison, website syd.gg, AS212071, AS212071:AS-ALL, Content network type, 100-1000 Mbps traffic, mostly outbound ratio, North America scope, selective policy, geofeed note, and public BGP.Exchange entries.
Domain of operation
SYDMAE is the public network operating identity for AS212071, a small content-oriented autonomous system associated with Sydney Morrison. It appears in RIPE/RDAP, PeeringDB, and routing mirrors, with selective peering, upstream transit to providers such as The Constant Company, and address space labeled under CloudExis. The entity is not verified as a standalone incorporated company, and its commercial model remains undocumented in public sources.
- Registry RDAP / WHOIS record: public-source identity and registry context for SYDMAE. Evidence basis: source-d9a7c4d43dc3
Timeline
- SYDMAE public evidence observed
Changes to SYDMAE's AS212071 registry object, route policies, upstream selections, BGP.Exchange presence, or geofeed references can shift reachability and attribution for the associated address space. Network operators, IP intelligence vendors, and geolocation services rely on these public signals when making routing and validation decisions.
At A Glance
- Name: SYDMAE
- Type: Network-related institution
- Base: United States
- Profile focus: Institution
What It Does
- public operating records
- official service pages
- source-backed relationship updates
Why It Matters
- The accuracy of SYDMAE's public records directly impacts the routing and classification of its announced IPv4 prefixes. Inaccurate or stale information could lead to reachability issues, misrouting, or incorrect geolocation, affecting downstream services that depend on the address space, even if the network itself is small.
- Operational criticality: Medium
- Time horizon: Next quarter
What To Watch
- official company sources
- public registries
- operator-published records
Track verified source updates, role changes, and current public evidence.
The accuracy of SYDMAE's public records directly impacts the routing and classification of its announced IPv4 prefixes. Inaccurate or stale information could lead to reachability issues, misrouting, or incorrect geolocation, affecting downstream services that depend on the address space, even if the network itself is small.
Longer-term relevance depends on verified operating, policy, and relationship changes.
Member Briefing
Deeper Profile Context
Login is required to unlock the full profile briefing and source notes.
Only for Strategy Circle
Strategic Circle Access
Open to all readers. Unlock profile briefings after joining and logging in.
Join Strategic CircleOnly for Leadership Alliance
Leadership Alliance Access
For owners and management of IP-holding companies. Login required to unlock.
Join Leadership AlliancePublic View
The accuracy of SYDMAE's public records directly impacts the routing and classification of its announced IPv4 prefixes. Inaccurate or stale information could lead to reachability issues, misrouting, or incorrect geolocation, affecting downstream services that depend on the address space, even if the network itself is small.
Watchpoints
- SYDMAE represents a small but technically consequential autonomous network.
- Its importance is not scale but the dependency that other networks and IP intelligence systems have on its routing posture.
- Changes to its registry, BGP, or geofeed can ripple through reachability and geolocation.
Caveats
- Public evidence is used only for source-backed claims.
- Private control or contract claims require separate public support.
FAQ
Why does BTW track SYDMAE?
Changes to SYDMAE's AS212071 registry object, route policies, upstream selections, BGP.Exchange presence, or geofeed references can shift reachability and attribution for the associated address space. Network operators, IP intelligence vendors, and geolocation services rely on these public signals when making routing and validation decisions.
What evidence supports the profile?
public-source identity and registry context for SYDMAE.
What should readers watch next?
SYDMAE represents a small but technically consequential autonomous network.






