Skip to main content

AS33724

BIZNESSHOSTING-DBA-VOLICO

VOLICO

Registry

Authoritative registration data

AS number
33724
Name
BIZNESSHOSTING-DBA-VOLICO
Organisation
VOLICO
Country
—
RIR
ARIN
Registered
Source:asn:rdap retrieved

IPv4 prefixes

82

IPv6 prefixes

5

Total announced

87

Announced prefixes

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

Prefixes announced by AS33724
173.246.32.0/19 IPv4 /19 not checked
104.222.96.0/20 IPv4 /20 not checked
173.246.32.0/20 IPv4 /20 not checked
173.246.48.0/20 IPv4 /20 RPKI not found
67.23.64.0/20 IPv4 /20 not checked
104.222.96.0/21 IPv4 /21 not checked
162.217.200.0/21 IPv4 /21 RPKI not found
204.11.232.0/21 IPv4 /21 not checked
204.13.0.0/21 IPv4 /21 RPKI not found
206.253.168.0/21 IPv4 /21 RPKI not found
208.64.64.0/21 IPv4 /21 RPKI not found
208.68.232.0/21 IPv4 /21 RPKI not found
208.88.120.0/21 IPv4 /21 RPKI not found
67.23.64.0/21 IPv4 /21 not checked
67.23.72.0/21 IPv4 /21 not checked
104.222.104.0/22 IPv4 /22 not checked
162.217.200.0/22 IPv4 /22 not checked
162.217.204.0/22 IPv4 /22 RPKI not found
199.59.96.0/22 IPv4 /22 RPKI not found
204.11.232.0/22 IPv4 /22 RPKI not found
204.11.236.0/22 IPv4 /22 RPKI not found
204.13.0.0/22 IPv4 /22 RPKI not found
204.13.4.0/22 IPv4 /22 RPKI not found
204.9.244.0/22 IPv4 /22 not checked
204.9.64.0/22 IPv4 /22 not checked
206.253.168.0/22 IPv4 /22 RPKI not found
206.253.172.0/22 IPv4 /22 not checked
208.64.64.0/22 IPv4 /22 not checked
208.64.68.0/22 IPv4 /22 RPKI not found
208.66.192.0/22 IPv4 /22 not checked
208.68.232.0/22 IPv4 /22 not checked
208.68.236.0/22 IPv4 /22 RPKI not found
208.73.224.0/22 IPv4 /22 not checked
208.88.120.0/22 IPv4 /22 not checked
208.88.124.0/22 IPv4 /22 RPKI not found
208.94.132.0/22 IPv4 /22 RPKI not found
104.152.56.0/23 IPv4 /23 RPKI not found
104.222.100.0/23 IPv4 /23 RPKI not found
199.59.96.0/23 IPv4 /23 RPKI not found
199.59.98.0/23 IPv4 /23 not checked
204.9.64.0/23 IPv4 /23 RPKI not found
204.9.66.0/23 IPv4 /23 RPKI not found
205.196.80.0/23 IPv4 /23 not checked
205.196.82.0/23 IPv4 /23 RPKI not found
205.196.84.0/23 IPv4 /23 RPKI not found
205.196.86.0/23 IPv4 /23 not checked
208.66.192.0/23 IPv4 /23 RPKI not found
208.66.194.0/23 IPv4 /23 not checked
208.73.224.0/23 IPv4 /23 not checked
208.73.226.0/23 IPv4 /23 not checked
208.94.132.0/23 IPv4 /23 RPKI not found
208.94.134.0/23 IPv4 /23 RPKI not found
8.6.240.0/23 IPv4 /23 RPKI not found
142.147.60.0/24 IPv4 /24 not checked
162.217.200.0/24 IPv4 /24 RPKI not found
170.39.103.0/24 IPv4 /24 RPKI not found
170.55.165.0/24 IPv4 /24 not checked
173.246.33.0/24 IPv4 /24 not checked
173.246.34.0/24 IPv4 /24 RPKI not found
173.246.37.0/24 IPv4 /24 not checked
173.246.43.0/24 IPv4 /24 not checked
173.246.44.0/24 IPv4 /24 not checked
173.246.49.0/24 IPv4 /24 RPKI not found
173.246.53.0/24 IPv4 /24 RPKI not found
173.246.59.0/24 IPv4 /24 not checked
173.246.60.0/24 IPv4 /24 not checked
173.246.61.0/24 IPv4 /24 not checked
204.11.236.0/24 IPv4 /24 not checked
208.68.238.0/24 IPv4 /24 not checked
208.94.132.0/24 IPv4 /24 RPKI not found
208.94.134.0/24 IPv4 /24 not checked
208.94.135.0/24 IPv4 /24 not checked
38.100.193.0/24 IPv4 /24 RPKI not found
64.139.130.0/24 IPv4 /24 RPKI not found
64.139.148.0/24 IPv4 /24 not checked
67.23.65.0/24 IPv4 /24 not checked
67.23.68.0/24 IPv4 /24 RPKI not found
67.23.71.0/24 IPv4 /24 RPKI not found
67.23.74.0/24 IPv4 /24 not checked
67.23.78.0/24 IPv4 /24 not checked
8.6.240.0/24 IPv4 /24 not checked
8.6.241.0/24 IPv4 /24 RPKI not found
2607:f3c8::/32 IPv6 /32 not checked
2607:f3c8:8000::/33 IPv6 /33 not checked
2607:f3c8::/33 IPv6 /33 RPKI not found
2607:f3c8:6000::/35 IPv6 /35 RPKI not found
2604:240:1::/48 IPv6 /48 RPKI valid

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 AS33724
Address families
Equinix Miami 10,000 Mbps IPv4 · IPv6
FL-IX 10,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 AS33724 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

23 networks seen before AS33724 in AS paths

Observed upstreams
Families
AS2914 NTT-DATA-2914 415 5,650
v4 v6
AS3356 LEVEL3 475 4,848
v4 v6
AS174 COGENT-174 676 4,534
v4 v6
AS3257 GTT-BACKBONE 540 3,085
v4 v6
AS6939 HURRICANE 199 2,555
v4 v6
AS3303 SWISSCOM 16 1,037
v4 v6
AS14840 ASN14840 10 465
v4 v6
AS35280 F5 9 286
v4 v6
AS137409 GSLNETWORKS-AS-AP 14 277
v4
AS4230 ASN4230 4 144
v4
AS9304 HUTCHISON-AS-AP 9 108
v4
AS52320 52320 6 96
v4 v6
AS7195 7195 6 95
v4 v6
AS64126 64126 5 90
v4
AS6057 6057 10 84
v4 v6
AS1031 PEER1-1031 2 80
v4
AS286 KPN 6 64
v4 v6
AS61568 ASN61568 4 54
v4 v6
AS58453 CMI-INT-HK 1 32
v4
AS37468 ORG-AC4-AFRINIC 4 8
v4
AS22356 ASN22356 3 8
v4 v6
AS264409 ASN264409 1 2
v4
AS23520 LIBERTY-NETWORKS 1 1
v4

No rows match “”.

Showing – of

Observed downstreams

6 networks seen after AS33724 in AS paths

Observed downstreams
Families
AS26687 JHS-CORP 323 1,974
v4
AS394002 WONDERLINK-COMMUNICATIONS 273 1,645
v4
AS402573 GAIA-01 269 329
v4
AS263170 263170 268 328
v4
AS395951 ZIPDATA 15 18
v4
AS4227858446 1 1
v4

No rows match “”.

Showing – of

Uncertain adjacencies

12 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS19151 BBO-1 5 192
v4 v6
AS20080 AMPATH 6 95
v4 v6
AS1828 UNITAS 5 93
v4 v6
AS9002 RETN-AS 5 93
v4 v6
AS24482 SGGS-AS-AP 5 93
v4 v6
AS51185 MAINSTREAMING-AS 5 93
v4 v6
AS199524 GCORE 5 93
v4 v6
AS13786 SEABORN 1 51
v4
AS36236 NETACTUATE 1 51
v4
AS61573 ASN61573 1 51
v4
AS263152 ASN263152 1 51
v4
AS263237 263237 1 51
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.