Netcore

A new foundation for decentralized apps with direct, secure, real-time device communication.

[Netcore @netcore_inc]

BREAKING NEWS 🚨📰

Keep watching to see what we’ve been up to 👀

[Netcore @netcore_inc]

Building in crypto doesn’t automatically mean infra is decentralized.

The assets may live on decentralized networks. But traditional infrastructure risks still apply if the exchange itself depends on centralized cloud providers, physical datacenters, and single coord layers.

[Coinbase Support @CoinbaseSupport]

On May 7th Coinbase experienced service disruptions. Here’s a quick summary of what happened:

→ Around 8PM ET, Coinbase systems flagged high error rates across multiple services.
→ We traced these errors to amazon failures in Availability Zone (use1-az4) in the AWS US-EAST-1 Region.
→ Coinbase systems are designed to be resilient to a single zone outage, and are designed to recover quickly if this happens.
→ In this case, we observed failures impacting multiple AWS zones, which caused an extended outage of core trading services.
→ Coinbase users experienced an extended outage while the AWS team worked to restore temperature controls and other Amazon Managed Services.

This primary issue is now fully resolved - thank you for your patience. If you have any outstanding questions about your account, please reach out to Coinbase Support, we’re ready to help.

Our team will conduct a full analysis. Details may change as our investigation progresses and more information is received from AWS’s official retrospective, once published.

[Netcore @netcore_inc]

This outage highlights a bigger infrastructure issue.

When critical systems rely on centralized cloud environments, even strong redundancy can still inherit physical datacenter risks. An overheated room should not have the power to disrupt major financial infrastructure.

[Brian Armstrong @brian_armstrong]

We experienced an outage at Coinbase last night, which is never acceptable. The root cause was a room overheating in an AWS datacenter when multiple chillers failed. We design our services to be redundant to downtime in any one AWS Availability Zone (AZ), and most of our systems worked this way last night, but not all.

Our centralized exchange did not. Exchanges have unique architectures that optimize for latency and co-location of clients. It is possible to make exchanges resistant to AZ failures, but this can introduce latency delays that are not desirable along with breaking customer co-location. Given this incident, we'll revisit these tradeoffs to ensure we're giving you the best possible venue to trade. At a minimum, the duration of an outage should be able to be reduced considerably when an AZ move is needed.

Thank you to the AWS and Coinbase teams for working through the night to mitigate the issue. We’ll share the detailed technical summary once it's ready.

[Netcore @netcore_inc]

Come grab your copy of The Netcore News at @devworld_conf Day 2 🗞️

[Netcore @netcore_inc]

Just wrapped Day 1 at DevWorld Amsterdam.

Met incredible builders, had sharp conversations, and one thing is clear: developers are actively looking for better infrastructure, stronger privacy, and systems that actually scale.

Day 2 let's gooo!

[Netcore @netcore_inc]

@delveroin https://t.co/Qvp5He0OhA

[bella @bella_cor3]

just udp things

[Netcore @netcore_inc]

@TTrimoreau security

[Netcore @netcore_inc]

@TTrimoreau privacy

[Netcore @netcore_inc]

The cloud didn’t solve networking ... it centralized it

[Netcore @netcore_inc]

Every app today: device → cloud → device

Netcore: device → device

That difference is everything.

[Netcore @netcore_inc]

@CliftonSellers Your backend without the backend

[Netcore @netcore_inc]

@CiprianiRanieri https://t.co/Qvp5He1m78

[Netcore @netcore_inc]

"Minecraft", fully decentralized built on Netcore.

https://t.co/9Su1QLUROU

[Kevin Murray @BL0CKCHAINKEV]

all of this is accurate. the architecture genuinely is excellent.

the one thing worth knowing is that Tailscale's control plane is still theirs.... the mesh is peer-to-peer but the coordination layer isn't. if that matters to you (and for a lot of teams it increasingly does) the true self-hosted path is worth looking at.

we built @netcore_inc around the same WireGuard + mesh primitives but with no third-party coordination. curious what the thread thinks about that tradeoff.

[Kevin Murray @BL0CKCHAINKEV]

@CR1337 And when you want to access with multiple devices or remotely without your data leaving devices.. you need @netcore_inc

[Kevin Murray @BL0CKCHAINKEV]

What is the ULTIMATE privacy stack?

Everything starts with @netcore_inc imo

[Kevin Murray @BL0CKCHAINKEV]

When your @netcore_inc swag and @PUMA are in sync 👌🏻

[Netcore @netcore_inc]

https://t.co/Qvp5He0OhA

[Netcore @netcore_inc]

we built insanely powerful devices

and then made them dependent on outdated infra