Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the isppro domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /data2/html/wp-dev.fiberxl.com/wp-includes/functions.php on line 6170

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wpforms-lite domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /data2/html/wp-dev.fiberxl.com/wp-includes/functions.php on line 6170

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the ultranet domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /data2/html/wp-dev.fiberxl.com/wp-includes/functions.php on line 6170

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the ultranet domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /data2/html/wp-dev.fiberxl.com/wp-includes/functions.php on line 6170

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wordpress-seo domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /data2/html/wp-dev.fiberxl.com/wp-includes/functions.php on line 6170

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the breadcrumb-navxt domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /data2/html/wp-dev.fiberxl.com/wp-includes/functions.php on line 6170

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the ultranet-core domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /data2/html/wp-dev.fiberxl.com/wp-includes/functions.php on line 6170

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the ultranet domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /data2/html/wp-dev.fiberxl.com/wp-includes/functions.php on line 6170
comparative-services - FiberXL

comparative-services

So why is it so great if something goes wrong and I call FiberXL?

Your typical great big telecomm company has a call center staffed with hundreds of response technicians. They usually are not really all that well trained. Sure, they’ll give you a “trouble ticket” right away, but a lot of them don’t really know that much about the underlying technology. We do.

Because we use superior technology (optical fiber in concert with Cisco and/or Ubiquiti routers and switches) we can construct robust systems where problems are rare. And we’re exclusive to downtown Chicago and places easily reachable from that locale. We’re not spread out all over the place and all our technicians know all our buildings.

Two of our three principle “technicians” (who are owners) are Ph.D.’s in experimental particle physics. Our third principle “technician” (also an owner) spent more than a decade developing an ISP in Bangkok with over 50 buildings under service. The physicists have been using computers heavily since the mid 80′s and we’ve been sending emails since the mid 80′s too. We remember when the internet was just email and 95% academic users. We’ve grown up with the internet, we’ve done networking for decades. We’ve seen all the big innovations from the ground up and we understand them from the inside out.

Our reserve technician has basically the same Ph.D. in particle physics background, also.

Our emergency 2 reserve technicians (who are close personal friends/relatives of the owners) both have college degrees in scientific fields and have also been programming and fixing networking problems for decades.