Xplore outages and service status in County of Camrose No. 22, Alberta
Service-wide status: Xplore
No problems detected
If you are having issues, please submit a report below.
- Xplore generated 0 outage signals in the last 24 hours around County of Camrose No. 22, including 0 direct reports.
Xplor (formerly known as Xplornet) is a Canadian wireless carrier and rural internet service provider. It is the largest rural fixed wireless broadband service provider in the country. Offers wireless internet services using satellite or 4G technology.
Problems in the last 24 hours in County of Camrose No. 22, Alberta
Xplore signals over the past 24 hours, with local activity from County of Camrose No. 22, Alberta and nearby areas. The dashed baseline applies to service-wide activity, not to local outage confirmation.
- Service-wide signals
- Service-wide baseline
At the moment, we haven't detected any problems at Xplore. Are you experiencing issues or an outage? Leave a message in the comments section!
Community Discussion
Tips? Frustrations? Share them here. Useful comments include a description of the problem, city and postal code.
Beware of "support numbers" or "recovery" accounts that might be posted below. Make sure to report and downvote those comments. Avoid posting your personal information.
Xplore Issues Reports Near County of Camrose No. 22, Alberta
Latest outage, problems and issue reports in County of Camrose No. 22 and nearby locations:
-
B.J. Normand (@BJ_Normand) reported from County of Camrose No. 22, Alberta@Xplornet any upgrades to service coming to Meeting Creek area? 8am my speed drops to a trickle.
Xplore Issues Reports
Latest outage, problems and issue reports in social media:
-
🇨🇦Dave Nussbaumer (@DaveNuss17) reported from Yorkton, Saskatchewan@OrenCairns Best thing I did 2 years ago….and I had the business package from Xplornet….and they had zero service skills!
-
Lomaxcat (@VoosieVooters) reported@xplore_ca I'm getting latency of 1.5s with my Xplore service. Not much of a bargain.
-
xIAmTurbox (@xIAmTurbox) reported@xplore_ca Maybe fix your outages ànd notify your customers
-
Commissioner Miner (@fanCRTCProfling) reportedAlternative explanation: These people use Xplornet that never works. These people used to hitting send 9 times for everything. A product of their "world Class" Canadian Communications. This is likely the best explanation and "OpenMedia" was honest enough to show it. #CRTC
-
Injured At Work (@WarMistweet) reported@xplore_ca Room for a tower for service at Attridge bus lines for South Cambridge?
-
Johnny ❄ ᔮᓂ ᖃᓴᓪᓗᐊᖅ (@JohnnyKasudluak) reportedLooks like you can't just cancel your xplornet services on you own via their website, they make you call them. Website navigation seems intentional, hard to find. Had to Google search about cancelation in order to find out it is over the phone only. Is that legal? 1/2
-
Ally Bryant (@Eh_Bee_Sea) reportedNo one answering @xplore_ca "24-7" customer support line. 3 or 4 tries in the last week... on hold indefinitely. The same song plays over and over and over. Email support? Auto-reply that a "case has been opened" with no details or information about actually getting service.
-
🎃CelticMagician🎃🏳️🌈 (@CelticMagician) reportedIt may not seem like a lot, but we legit have not had this problem since our days with Xplornet. Starlink, you doing okay buddy? The occasional hiccup is a given because of trees, but that wasn't what this was. :/
-
AtomicHydra (@atomic_hydra) reported@xplore_ca Why ******** do i need to wait until 1AM to get good internet this is dumb as ****.
-
Tybernicus (@Tybernicus17) reported@MajJensen3 @OJoelsen Why would he? In 2021 I bought a house on a paved road 6kms from a small town. Not even Xplornet was available. Cell signal very weak. If not for Starlink, I and many others would have no internet access.
Xplore detected incident history
These records describe service-wide increases in reported problems. They do not confirm an outage at every address. Recorded end times describe our detection window, not a provider-confirmed repair.
-
Detected:
Detection ended: (26 minutes) -
Detected:
No end recorded. This alone does not establish the current status. -
Detected:
No end recorded. This alone does not establish the current status. -
Detected:
Detection ended: (289 minutes) -
Detected:
Detection ended: (17 minutes) -
Detected:
No end recorded. This alone does not establish the current status.
Xplore outage reports by location
Choose a location to check local Xplore reports and activity.