Skip to main content

AS211399

DIGITALKPD-AS

IRR =AS-DIGITALKPD

Registry

Authoritative registration data

AS number
211399
Name
DIGITALKPD-AS
Organisation
IRR =AS-DIGITALKPD
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

3

IPv6 prefixes

0

Total announced

3

Announced prefixes

Observed in BGP by route collectors, not a registry allocation list

Prefixes announced by AS211399
46.8.204.0/23 IPv4 /23 not checked
46.8.140.0/24 IPv4 /24 not checked
46.8.148.0/24 IPv4 /24 not checked

No rows match “”.

Showing of

Source:ripestat:announced-prefixes observed

Internet Exchanges

Exchanges where this network has a listed peering LAN connection

Internet Exchange memberships listed for AS211399
Address families
Eurasia Peering IX: Peering LAN 10,000 Mbps IPv4
GNM-IX 10,000 Mbps IPv4
Global-IX 10,000 Mbps IPv4
PITER-IX Frankfurt 10,000 Mbps IPv4
PITER-IX Helsinki 10,000 Mbps IPv4
PITER-IX Moscow: MSK_PEERING_VLAN 10,000 Mbps IPv4
PITER-IX Saint-Petersburg: SPB_PEERING_VLAN 10,000 Mbps IPv4

No rows match “”.

Showing of

Source:peeringdb retrieved

Exchange membership means the network has a listed connection; it does not prove peering with other members.

Observed adjacencies

Networks seen next to AS211399 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

15 networks seen before AS211399 in AS paths

Observed upstreams
Families
AS50509 124 468
v4
AS8641 76 291
v4
AS31500 70 264
v4
AS8218 NEO-ASN 2 24
v4
AS25091 IP-Max 4 21
v4
AS47692 2 12
v4
AS39351 ESAB-AS 2 6
v4
AS6204 1 3
v4
AS6663 1 3
v4
AS9198 1 3
v4
AS12695 DINET-AS 1 3
v4
AS15958 1 3
v4
AS42295 TBISS-AS 1 3
v4
AS60171 1 3
v4
AS137409 GSLNETWORKS-AS-AP 1 3
v4

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS211399 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

15 adjacencies that may be an artefact of collector peering

No rows match “”.

Showing of

Note:
These are observed adjacencies derived from BGP path data, not confirmed commercial relationships. A network appearing before another in an AS path does not establish that it is a paying transit customer, a settlement free peer, or anything else contractual. Adjacencies marked uncertain were seen only as direct peers of a route collector, so the collector's own peering may have created them.