Skip to main content

AS32563

ASN-SRCMTL

Canadian Broadcasting Corporation

Registry

Authoritative registration data

AS number
32563
Name
ASN-SRCMTL
Organisation
Canadian Broadcasting Corporation
Country
—
RIR
ARIN
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 AS32563
159.33.128.0/19 IPv4 /19 not checked
159.33.64.0/19 IPv4 /19 not checked
159.33.80.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 AS32563
Address families
CANIX Montreal 4,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 AS32563 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

3 networks seen before AS32563 in AS paths

Observed upstreams
Families
AS6461 ZAYO-6461 261 821
v4
AS812 ROGERS-COMMUNICATIONS 57 130
v4
AS6939 HURRICANE 23 48
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS32563 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

5 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS49544 i3Dnet 1 4
v4
AS1403 EBOX 1 2
v4
AS22652 FIBRENOIRE-INTERNET 1 2
v4
AS35280 F5 1 2
v4
AS36236 NETACTUATE 1 2
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.