Country
—
ASN LANDING PAGE
AS213619
NETBELA-AS Tom Emming trading as Netbela
Last updated · Jul 20, 2026
Total prefixes
4
IPv4 prefixes
2
IPv6 prefixes
2
ASN summary
How to read the scale of AS213619
NETBELA-AS Tom Emming trading as Netbela currently reports 4 prefixes and 20 upstream, downstream, or peer relationships. These counts describe the current dataset; they do not by themselves prove network quality, reach, or service use.
What can an ASN page answer?
An ASN page shows the public organization label, country or region, BGP prefixes, and available peer and upstream relationships. It adds network context but cannot confirm a website host, physical facility, security status, or service quality.
How should you read the organization and region fields?
NETBELA-AS Tom Emming trading as Netbela is currently associated with an unknown region. These values come from public network sources and are useful lookup clues; an organization label, registration region, and actual service location may differ.
How should you verify the AS213619 result?
The page shows ASN data returned by the current upstream query; interpret it with the update time. Open representative IP pages from the same network and compare prefixes, source labels, and query times. Verify operator or service claims with the relevant registry or network operator.
How to verify this ASN result
AS213619 ASN lookupAS213619 BGPAS213619 peersAS213619 prefixesAS213619 upstreamsNETBELA-AS Tom Emming trading as Netbela ASN
Upstreams
Detailed data for this ASN is not available right now.
Downstreams
Detailed data for this ASN is not available right now.
Peers
AS50917
AS50917
—
AS35133
AS35133
—
AS211623
AS211623
—
AS6939
AS6939
—
AS20764
AS20764
—
AS50304
AS50304
—
AS50629
AS50629
—
AS12859
AS12859
—
AS24961
AS24961
—
AS3399
AS3399
—
AS6663
AS6663
—
AS24482
AS24482
—
AS28917
AS28917
—
AS36236
AS36236
—
AS39122
AS39122
—
AS41327
AS41327
—
AS56655
AS56655
—
AS56911
AS56911
—
AS199524
AS199524
—
AS209823
AS209823
—
Prefix inventory
| Prefix | Name | Country |
|---|---|---|
| 193.29.181.0/24 | AS213619 | — |
| 2a11:1400:3000::/48 | AS213619 | — |
| 2a13:9500:1b6::/48 | AS213619 | — |
| 82.152.179.0/24 | AS213619 | — |
Related ASN pages
AS15169 · Google
Review Google network organization fields, prefixes, peers, upstreams, and downstreams.
AS13335 · Cloudflare
Review Cloudflare network organization fields, prefixes, peers, upstreams, and downstreams.
AS8075 · Microsoft
Review Microsoft network organization fields, prefixes, peers, upstreams, and downstreams.
AS16509 · Amazon
Review Amazon network organization fields, prefixes, peers, upstreams, and downstreams.
Related lookups and next steps
Frequently asked questions about this ASN page
What does AS213619 represent?
AS213619 is an autonomous system number. The current source associates it with NETBELA-AS Tom Emming trading as Netbela and the region field an unknown region; those values add network context but do not prove a specific service, physical location, or quality level.
What are peers, upstreams, and prefixes useful for on the AS213619 page?
They help explain the scale, interconnection depth, and route structure of AS213619. Richer peering and upstream data often indicate broader network reach, but they should still be interpreted together with prefixes and related IP landing pages.
What should you do after reviewing AS213619?
Open a concrete IP page to check how the address maps into AS213619, then compare the prefix, source labels, and query time. Verify operator or service claims with the relevant registry or network operator.
Related topics
BGP and ASN Basics Guide
Use real IP and ASN pages to understand ASNs, BGP prefixes, peers, upstreams, and downstreams, including the limits of each snapshot.
Routing Troubleshooting and Network Analysis
Build troubleshooting context from an IP, BGP prefix, ASN, and public network relationships without treating static route data as a packet path.
Cloud Network and ASN Comparison
Compare representative cloud and edge networks by ASN, announced prefixes, peers, upstreams, and downstreams without inferring a specific host or customer workload.