Skip to main content

AS210021

DIL

DIL Technology Limited

Registry

Authoritative registration data

AS number
210021
Name
DIL
Organisation
DIL Technology Limited
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

18

IPv6 prefixes

4

Total announced

22

Announced prefixes

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

Prefixes announced by AS210021
185.100.23.0/24 IPv4 /24 not checked
185.206.172.0/24 IPv4 /24 not checked
185.206.173.0/24 IPv4 /24 not checked
185.206.174.0/24 IPv4 /24 not checked
185.206.175.0/24 IPv4 /24 not checked
185.206.80.0/24 IPv4 /24 not checked
185.206.81.0/24 IPv4 /24 not checked
185.206.82.0/24 IPv4 /24 not checked
185.206.83.0/24 IPv4 /24 not checked
185.253.77.0/24 IPv4 /24 not checked
185.75.99.0/24 IPv4 /24 not checked
194.127.111.0/24 IPv4 /24 not checked
31.14.229.0/24 IPv4 /24 not checked
31.14.230.0/24 IPv4 /24 not checked
31.14.231.0/24 IPv4 /24 not checked
86.105.144.0/24 IPv4 /24 not checked
86.105.145.0/24 IPv4 /24 not checked
86.105.146.0/24 IPv4 /24 not checked
2a05:27c0:1::/48 IPv6 /48 not checked
2a05:27c0:2::/48 IPv6 /48 not checked
2a05:27c0:4::/48 IPv6 /48 not checked
2a05:27c0::/48 IPv6 /48 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 AS210021
Address families
BIX.BG: Main 100,000 Mbps IPv4 · IPv6
DE-CIX Istanbul: DE-CIX Istanbul Peering LAN 100,000 Mbps IPv4 · IPv6
NetIX: NetIX 100,000 Mbps IPv4 · IPv6

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 AS210021 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

30 networks seen before AS210021 in AS paths

Observed upstreams
Families
AS1299 TWELVE99 10,398 50,261
v4 v6
AS6939 HURRICANE 2,659 14,742
v4 v6
AS6453 AS6453 3,536 13,010
v4 v6
AS3356 LEVEL3 3,280 11,278
v4 v6
AS174 COGENT-174 2,027 9,375
v4 v6
AS12735 ASTurkNet 1,534 6,226
v4 v6
AS25091 IP-Max 563 3,616
v4 v6
AS8218 NEO-ASN 98 1,854
v4 v6
AS3303 SWISSCOM 437 1,592
v4 v6
AS213642 368 1,565
v4
AS5405 283 957
v4 v6
AS60068 116 803
v4 v6
AS200612 GulfBridgeInternational 156 477
v6
AS137409 GSLNETWORKS-AS-AP 133 435
v4 v6
AS6663 81 338
v4 v6
AS14840 ASN14840 33 334
v4 v6
AS15958 71 233
v4
AS8280 68 231
v4 v6
AS20764 RASCOM-AS 55 160
v4 v6
AS51095 21 115
v4 v6
AS29632 NASSIST-AS 38 79
v6
AS22356 31 76
v4 v6
AS6204 27 70
v4
AS9498 BBIL-AP 9 23
v4
AS21215 7 18
v4
AS8717 4 10
v4
AS8866 VIVACOM-AS 2 8
v6
AS211288 NETASSISTBG 1 5
v6
AS9009 M247 2 2
v4
AS263444 1 1
v4

No rows match “”.

Showing of

Observed downstreams

22 networks seen after AS210021 in AS paths

Observed downstreams
Families
AS211513 15,364 59,798
v4 v6
AS208293 3,678 32,464
v4 v6
AS59625 504 5,072
v4 v6
AS211181 1,485 4,034
v4 v6
AS215597 842 2,834
v4 v6
AS215160 369 1,685
v4 v6
AS210413 787 1,379
v4
AS213098 266 1,360
v4
AS14789 CLOUDFLARENET 357 667
v4 v6
AS211413 263 338
v4
AS54994 ML-1432-54994 265 337
v6
AS207097 261 337
v4
AS57761 251 337
v4
AS200654 264 334
v4
AS12735 ASTurkNet 92 319
v6
AS200612 GulfBridgeInternational 50 73
v4 v6
AS1299 TWELVE99 30 71
v6
AS210767 18 71
v4 v6
AS6453 AS6453 22 51
v6
AS3356 LEVEL3 11 35
v6
AS61271 12 14
v4
AS174 COGENT-174 1 1
v6

No rows match “”.

Showing of

Uncertain adjacencies

7 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS49544 i3Dnet 75 471
v4 v6
AS13004 78 273
v4 v6
AS208972 62 264
v4 v6
AS44901 72 231
v4
AS212483 level86 18 138
v4 v6
AS198150 SIACOM-AS 18 71
v4 v6
AS29049 13 46
v4

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.