Skip to main content

AS803

SASKTEL

Saskatchewan Telecommunications

Registry

Authoritative registration data

AS number
803
Name
SASKTEL
Organisation
Saskatchewan Telecommunications
Country
—
RIR
ARIN
Registered
Source:asn:rdap retrieved

IPv4 prefixes

44

IPv6 prefixes

3

Total announced

47

Announced prefixes

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

Prefixes announced by AS803
142.164.0.0/16 IPv4 /16 RPKI valid
142.165.0.0/16 IPv4 /16 not checked
204.83.0.0/16 IPv4 /16 not checked
71.17.0.0/16 IPv4 /16 RPKI valid
207.195.0.0/17 IPv4 /17 not checked
207.47.128.0/17 IPv4 /17 not checked
216.197.128.0/17 IPv4 /17 not checked
67.225.0.0/17 IPv4 /17 RPKI valid
69.11.0.0/17 IPv4 /17 not checked
64.110.192.0/18 IPv4 /18 RPKI valid
108.60.160.0/19 IPv4 /19 not checked
198.230.96.0/19 IPv4 /19 RPKI valid
206.163.224.0/19 IPv4 /19 not checked
216.174.128.0/19 IPv4 /19 not checked
64.201.192.0/19 IPv4 /19 not checked
68.69.192.0/19 IPv4 /19 not checked
108.160.16.0/20 IPv4 /20 RPKI valid
108.174.160.0/20 IPv4 /20 RPKI valid
198.245.112.0/20 IPv4 /20 RPKI valid
96.125.240.0/20 IPv4 /20 not checked
192.139.168.0/21 IPv4 /21 RPKI not found
192.34.224.0/21 IPv4 /21 RPKI valid
199.189.88.0/21 IPv4 /21 RPKI valid
104.152.28.0/22 IPv4 /22 not checked
104.219.8.0/22 IPv4 /22 not checked
104.255.48.0/22 IPv4 /22 RPKI valid
162.253.8.0/22 IPv4 /22 not checked
192.139.160.0/22 IPv4 /22 RPKI not found
198.73.60.0/22 IPv4 /22 not checked
198.73.64.0/22 IPv4 /22 not checked
216.126.200.0/22 IPv4 /22 not checked
74.113.12.0/22 IPv4 /22 RPKI valid
198.169.28.0/23 IPv4 /23 not checked
199.26.190.0/23 IPv4 /23 not checked
142.165.219.0/24 IPv4 /24 not checked
192.139.164.0/24 IPv4 /24 not checked
192.139.167.0/24 IPv4 /24 not checked
192.139.185.0/24 IPv4 /24 not checked
192.219.119.0/24 IPv4 /24 RPKI not found
192.75.185.0/24 IPv4 /24 not checked
198.169.239.0/24 IPv4 /24 RPKI not found
198.169.248.0/24 IPv4 /24 RPKI not found
198.73.82.0/24 IPv4 /24 not checked
208.77.143.0/24 IPv4 /24 RPKI valid
2607:f4a8::/32 IPv6 /32 RPKI valid
2607:f4a8:261::/48 IPv6 /48 RPKI valid
2620:19:2000::/48 IPv6 /48 RPKI not found

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 AS803
Address families
Equinix Chicago 100,000 Mbps IPv4 · IPv6
MICE: Shared Peering 100,000 Mbps IPv4 · IPv6
SIX Seattle: MTU 1500 200,000 Mbps IPv4 · IPv6
TorIX 100,000 Mbps IPv4 · IPv6
VANIX 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 AS803 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

16 networks seen before AS803 in AS paths

Observed upstreams
Families
AS6461 ZAYO-6461 1,975 22,270
v4 v6
AS174 COGENT-174 1,398 12,895
v4 v6
AS577 BACOM 1,351 7,484
v4 v6
AS6939 HURRICANE 241 2,229
v4 v6
AS399844 SASK-CNET 414 1,345
v4 v6
AS19523 BH-TELECOM-CORP 415 737
v4
AS3303 SWISSCOM 88 700
v4 v6
AS60068 CDN77 44 509
v4 v6
AS137409 GSLNETWORKS-AS-AP 39 394
v4 v6
AS9002 RETN-AS 32 323
v4 v6
AS394256 CLOUDSINGULARITY 18 147
v4 v6
AS7575 AARNET-AS-AP 11 99
v4
AS32621 TCV-511 11 99
v4 v6
AS8220 COLT 6 30
v4
AS20473 AS-VULTR 5 6
v6
AS52025 PARADOXNETWORKS-LIMITED 4 5
v4

No rows match “”.

Showing – of

Observed downstreams

25 networks seen after AS803 in AS paths

No rows match “”.

Showing – of

Uncertain adjacencies

11 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 22 430
v4 v6
AS49544 i3Dnet 17 282
v4 v6
AS36236 NETACTUATE 20 174
v4 v6
AS34927 iFog-GmbH 21 165
v4 v6
AS852 ASN852 21 154
v4 v6
AS22652 FIBRENOIRE-INTERNET 21 151
v4 v6
AS1828 UNITAS 18 147
v4 v6
AS835 GOCODEIT-EDGE 19 145
v4
AS35280 F5 14 134
v4
AS18106 VIEWQWEST-SG-AP 14 131
v4
AS1403 EBOX 5 12
v6

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.