Skip to main content

AS33604

BTNETWORK

Burlington Telecom

Registry

Authoritative registration data

AS number
33604
Name
BTNETWORK
Organisation
Burlington Telecom
Country
RIR
ARIN
Registered
Source:asn:rdap retrieved

IPv4 prefixes

5

IPv6 prefixes

1

Total announced

6

Announced prefixes

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

Prefixes announced by AS33604
65.183.128.0/19 IPv4 /19 not checked
69.5.112.0/20 IPv4 /20 not checked
204.13.40.0/21 IPv4 /21 not checked
162.247.88.0/22 IPv4 /22 not checked
38.69.196.0/22 IPv4 /22 not checked
2606:8600::/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 AS33604
Address families
Equinix Ashburn 20,000 Mbps IPv4 · IPv6
Equinix New York 20,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 AS33604 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

7 networks seen before AS33604 in AS paths

Observed upstreams
Families
AS6939 HURRICANE 733 2,961
v4 v6
AS174 COGENT-174 93 282
v4 v6
AS6057 6057 6 10
v4 v6
AS37468 ORG-AC4-AFRINIC 3 4
v4
AS60171 3 4
v4
AS137409 GSLNETWORKS-AS-AP 3 4
v4
AS7195 7195 1 1
v6

No rows match “”.

Showing of

Observed downstreams

2 networks seen after AS33604 in AS paths

Observed downstreams
Families
AS63276 CHAMPLAINCOLLEGE 266 669
v4
AS398045 272 380
v4

No rows match “”.

Showing of

Uncertain adjacencies

9 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 4 19
v4 v6
AS199524 GCORE 4 9
v4 v6
AS49544 i3Dnet 3 8
v4 v6
AS13786 3 5
v4 v6
AS36236 NETACTUATE 3 5
v4 v6
AS52320 52320 3 5
v4 v6
AS1828 UNITAS 3 4
v4
AS35280 F5 3 4
v4
AS37721 ORG-VTS1-AFRINIC 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.