Country
—
ASN LANDING PAGE
AS214380
TIM427 - Tim de Boer trading as tim427.net
Last updated · Apr 4, 2026
Total prefixes
3
IPv4 prefixes
2
IPv6 prefixes
1
ASN summary
How to read the scale of AS214380
TIM427 - Tim de Boer trading as tim427.net currently shows 3 prefixes and 40 upstream, downstream, or peer relationships. Larger prefix inventories often indicate broader network footprint, but they should still be read together with country and peering context.
When is an ASN page most useful?
ASN landing pages are more useful than a single IP page when you want cloud provider attribution, routing research, infrastructure comparison, or network topology analysis at the organization level.
How should you read the country, organization, and role of AS214380?
TIM427 - Tim de Boer trading as tim427.net is currently associated with an unknown region. Country data is only a starting point; the more important signals are the organization name, website, prefix volume, and peering relationships that reveal whether the network behaves like a cloud platform, ISP, CDN, or enterprise backbone.
What should you inspect next after the AS214380 page?
This page is currently showing live ASN data that can be used for peer, prefix, and network scale analysis. The most useful next step is usually to return to a related IP landing page, then compare that concrete address with this ASN profile and with broader topic pages for routing, cloud attribution, or WHOIS ownership analysis.
Search intents this ASN page helps cover
AS214380 ASN lookupAS214380 BGPAS214380 peersAS214380 prefixesAS214380 upstreamsTIM427 - Tim de Boer trading as tim427.net ASN
Upstreams
Detailed data for this ASN is not available right now.
Downstreams
Detailed data for this ASN is not available right now.
Peers
AS6939
AS6939
—
AS200132
AS200132
—
AS8283
AS8283
—
AS212635
AS212635
—
AS212895
AS212895
—
AS1101
AS1101
—
AS50869
AS50869
—
AS20764
AS20764
—
AS34019
AS34019
—
AS3216
AS3216
—
AS6057
AS6057
—
AS14840
AS14840
—
AS35280
AS35280
—
AS37100
AS37100
—
AS48362
AS48362
—
AS52320
AS52320
—
AS58057
AS58057
—
AS1140
AS1140
—
AS1764
AS1764
—
AS1828
AS1828
—
AS3333
AS3333
—
AS3399
AS3399
—
AS3462
AS3462
—
AS4230
AS4230
—
AS4455
AS4455
—
AS5405
AS5405
—
AS5713
AS5713
—
AS6424
AS6424
—
AS6663
AS6663
—
AS8529
AS8529
—
AS12637
AS12637
—
AS12779
AS12779
—
AS12859
AS12859
—
AS12969
AS12969
—
AS13237
AS13237
—
AS14630
AS14630
—
AS14907
AS14907
—
AS15547
AS15547
—
AS18106
AS18106
—
AS20932
AS20932
—
Prefix inventory
| Prefix | Name | Country |
|---|---|---|
| 193.22.87.0/24 | AS214380 | — |
| 2001:67c:139c::/48 | AS214380 | — |
| 44.32.106.0/23 | AS214380 | — |
Related ASN pages
AS15169 · Google
A strong reference ASN for Google DNS, Google Cloud, and global network footprint analysis.
AS13335 · Cloudflare
Useful for analyzing CDN, Anycast, WAF, and large-scale edge network behavior.
AS8075 · Microsoft
Helpful when comparing Azure, enterprise backbone, and large-cloud routing patterns.
AS16509 · Amazon
A useful ASN landing page for understanding AWS and large cloud-network ownership.
Related lookups and next steps
WHOIS vs ASN Ownership Guide
Continue from this ASN into the differences between WHOIS ownership and ASN ownership.
Routing Troubleshooting and Network Analysis
Continue from this ASN into route troubleshooting and network analysis.
Cloud Network and ASN Comparison
Useful when you want to compare this ASN against larger cloud and edge networks.
WHOIS and IP Ownership Guide
Continue from the ASN page into WHOIS and ownership verification.
Frequently asked questions about this ASN page
What does AS214380 represent?
AS214380 is an autonomous system number used to identify an independently operated network. The current page associates it with TIM427 - Tim de Boer trading as tim427.net in an unknown region, which helps determine whether it behaves like a cloud provider, ISP, CDN, or enterprise backbone.
What are peers, upstreams, and prefixes useful for on the AS214380 page?
They help explain the scale, interconnection depth, and route structure of AS214380. 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 AS214380?
The best next step is usually to return to a concrete IP landing page to see how a specific address maps into AS214380, then continue into cloud, WHOIS, or routing topic pages to understand the network in a broader context.
Related topics
WHOIS vs ASN Ownership Guide
Understand why WHOIS ownership and ASN ownership can differ, and how to combine both when deciding who really owns or operates an IP.
WHOIS and IP Ownership Guide
Use WHOIS, ASN, prefixes, and organization data to determine who ultimately owns an IP, range, or resolved domain target.
BGP and ASN Basics Guide
Learn what ASN, BGP routes, prefixes, upstreams, downstreams, and peers mean, then explore real ASN pages.
Cloud Network and ASN Comparison
Compare large cloud and edge networks such as Google, Cloudflare, Microsoft, and Amazon through their ASN landing pages.