安全验证

请完成以下验证以查看 ASN 详情

验证中...
BRENNERCOM-AS

AS20811

Transit Provider

BRENNERCOM-AS

16
IPv4 Prefixes
0
IPv6 Prefixes
68.9K
IPv4 Addresses
RIR
RIPE
Scope
Europe
Traffic
20-50Gbps
Ratio
Mostly Inbound
Peering
Selective
IRR AS-SET
AS-BCOMIT
Risk Score
25/100

Network Characteristics

Unknown IPv6 Enabled

宣告的前缀 (显示前 16 个)

前缀 网络类型 风险分 标签 首次发现
37.186.128.0/18 transit 25
-
2026-01-31
46.234.224.0/19 transit 25
-
2026-01-31
46.234.232.0/24 transit 25
-
2026-01-31
77.74.112.0/21 transit 25
-
2026-01-31
84.18.128.0/19 transit 25
-
2026-01-31
84.18.147.0/24 transit 25
-
2026-01-31
89.190.160.0/19 transit 25
-
2026-01-31
93.89.48.0/20 transit 25
-
2026-01-31
93.89.58.0/24 transit 25
-
2026-01-31
95.171.32.0/19 transit 25
-
2026-01-31
109.69.248.0/21 transit 25
-
2026-01-31
147.189.208.0/24 transit 25
-
2026-01-31
147.189.209.0/24 transit 25
-
2026-01-31
185.6.192.0/22 transit 25
-
2026-01-31
185.111.144.0/22 transit 25
-
2026-01-31
217.199.0.0/19 transit 25
-
2026-01-31

PeeringDB 备注

We have a selective peering policy and evaluate each request based on its merits. We also require from our peers: * common sense * must filter customer prefixes strictly * must not leak prefixes from non-customer sessions (even if the prefix is from a customer) * an updated peeringdb entry * reasonable prefix aggregation * responsive NOC * peers IX-link must not be congested * IPv6 peering, if peer AS is v6 enabled * must not be our customer, or a customer of a existing peer * do not send automated emails to our NOC for whatever reason; humans only! Peering through route servers is usually preferred over dedicated BGP sessions, especially for low-volume, low-prefix peers that are already connected to the route servers. This is to avoid unnecessary maintenance and configuration overhead. We filter all our customers with strict prefix-lists (along with other industry standard filtering and security measures), no exceptions.

API 调用

# 使用 cURL 查询此 ASN
curl -H "Authorization: Bearer YOUR_API_KEY" \
"https://ipv4.dev/api/v1/asn/20811"