Skip to main content

AS33302

D102-COS-1

Data102

Registry

Authoritative registration data

AS number
33302
Name
D102-COS-1
Organisation
Data102
Country
RIR
ARIN
Registered
Source:asn:rdap retrieved

IPv4 prefixes

11

IPv6 prefixes

1

Total announced

12

Announced prefixes

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

Prefixes announced by AS33302
198.95.96.0/20 IPv4 /20 not checked
216.84.240.0/20 IPv4 /20 not checked
64.111.16.0/20 IPv4 /20 not checked
96.47.0.0/20 IPv4 /20 not checked
8.20.216.0/21 IPv4 /21 not checked
192.187.196.0/22 IPv4 /22 not checked
192.187.204.0/22 IPv4 /22 not checked
208.80.0.0/23 IPv4 /23 not checked
209.136.66.0/23 IPv4 /23 not checked
64.111.17.0/24 IPv4 /24 not checked
96.47.7.0/24 IPv4 /24 not checked
2607:2800::/32 IPv6 /32 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 AS33302
Address families
IX-Denver: IX-Denver Fabric 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 AS33302 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

4 networks seen before AS33302 in AS paths

Observed upstreams
Families
AS6939 HURRICANE 2,225 11,514
v4 v6
AS174 COGENT-174 571 1,377
v4 v6
AS3356 LEVEL3 542 1,324
v4 v6
AS32621 TCV-511 1 2
v4

No rows match “”.

Showing of

Observed downstreams

5 networks seen after AS33302 in AS paths

Observed downstreams
Families
AS15221 1,367 5,866
v4 v6
AS29802 HVC-AS 534 1,824
v4 v6
AS40244 320 1,127
v4 v6
AS40343 288 494
v4 v6
AS395391 276 382
v4

No rows match “”.

Showing of

Uncertain adjacencies

1 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS1828 UNITAS 3 4
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.