Categories
Announcements Changes

Price Increases Effective February 1, 2022

Due to a majority of our suppliers increasing prices for various reasons over the last year, we will be raising some of our prices.

For all new service orders and change orders signed after February 1, 2022, existing customers that are past the end of their term agreement, and month-to-month customers, the following prices will be increasing 5%:

Full Rack Colocation Package

  • Old Price: $949.00
  • New Price: $996.45

Half Rack Colocation Package

  • Old Price: $449.00
  • New Price: $471.45

Shared Space Colocation

  • 1U: $99.00 (No Change)
  • 2U: $109.20
  • 3U: $117.60
  • 4U: $134.40
  • 5U: $145.95
  • 6U: $166.95
  • 7U: $198.45
  • 8U: $229.95
  • 9U: $250.95
  • 10U: $271.95

The included IPv4 subnet for shared space colocations will be changed from a /29 to a /30.

Custom Colocation Package Base Rates

Full Rack Base Rate

  • Old Price: $349.00
  • New Price: $366.45

Half Rack Base Rate

  • Old Price: $180.00
  • New Price: $189.00

Antenna Colocation

List prices for antenna colocation are remaining the same, but any customers currently receiving discounted rates for antenna colocation will be updated to current list price. We will also be normalizing all antenna colocation related charges into one of the three antenna classes; previously we would charge adjusted amounts for accessories.

Discounted Rates Carried Past End-of-Term

Any previously contracted discounts that have remained past the end of their term agreement will be removed, and current list price will be applied.

Work Rates

  • Work Rate (daytime hours): $99/hr
  • Work Rate (after hours or holiday): $199/hr

Prices for add-on items or demand charges – such as power, bandwidth, cross connects, outlets, ports, IP addresses, etc. – will remain unchanged. Setup fees will also remain unchanged.

If you are an existing customer under a term agreement your pricing WILL NOT change: the agreement protects you from price increases for the duration of the term.

Effective February 1, 2022 the new prices shown here supersede all other previously published pricing for the affected services, such as literature that was published prior to this date, quotes, service orders or change orders that are not signed by 5:00pm Pacific time on January 31, 2022, and any other places pricing may be shown that has not been updated due to error or omission.

For agreements that allow a term renewal, this only applies to the services originally contracted. Any new services or changes will be quoted with prices in effect at the time of the request. Renewal option must be exercised before term expiration.

Categories
Changes Status

SSL/TLS Changes

We’re going to start turning off TLSv1.0 and TLSv1.1 per best current practices (BCP 195), and start working on updates to add support for TLSv1.3. Our account control center is first. Other services will be changed as we work on configs or other updates for both web and mail services.

As of early 2020, support for TLS 1.0 and TLSv1.1 has been removed in current versions of major browsers. For more information about the depreciation of TLS1.0/1.1 see: https://blog.qualys.com/product-tech/2018/11/19/grade-change-for-tls-1-0-and-tls-1-1-protocols

We’re also changing our ACME client for Let’s Encrypt certificates. We started out using certbot, however certbot is moving to an app store framework (Snap) for future updates and we don’t want to install such things on our servers. So we searched for an alternative ACME client that we liked and settled on dehydrated. For more information on dehydrated visit them on github at: https://github.com/dehydrated-io/dehydrated

Categories
Announcements Changes

Peering at SFMIX

Now peering at SFMIX in the San Francisco “Silicon Valley” region of California. Roller Network has an open peering policy and we are happy to peer with networks of any size. We’re also on the route servers.

Categories
Announcements Changes Status

SquirrelMail End of Life Notice

Since the very beginning of our hosted mail service, SquirrelMail was there as a webmail option. It’s served thousands of users well, but the time has come where we need to declare SquirrelMail end of life (EOL) and no longer supported. SquirrelMail has not been actively developed for several years, and incompatibility with other upgrades we will be making across our system is very likely.

As an EOL service, we will no longer test changes for compatibility with SquirrelMail. Although the basic email functions of SquirrelMail will continue to function, any broken additional features in SquirrelMail will be removed or disabled.

We understand the desire for a simple webmail interface still exists in our customer base and we will be looking at replacement options. In the meantime, please plan to migrate your webmail needs to RoundCube at: https://webmail.rollernet.us/roundcube

SquirrelMail will be shut down on December 31, 2020.

Categories
Changes Status

System Updates 2020 Edition

Over the next several weeks are are going to try to get all of our systems updated to Debian 9 (oldstable) or ideally Debian 10 (stable) wherever possible. Many systems are still running Debian 8 LTS for which security support ends in June.

We will do our best to minimize disruptions. Any work that’s unavoidably disruptive will be performed during our weekly maintenance window every Saturday between 10:00 and 22:00. An example of a system that’s disruptive would be the account control center, webmail, or IMAP/POP3 hosted mail. To completely update a system there are required reboots, and in some cases (most notably IMAP/POP3 hosted mail), forced switches between active/standby pairs to verify functionality. Updates on our in-office system will cause interruptions to our phone and hotline number (which run on Asterisk) while we perform its upgrades. Email us if you don’t hear the voice prompts answer since someone will be watching for emails when we know voice is being worked on. Work to non-interactive systems like ns1/ns2 may be performed at any time since our supported configuration is that customers configure both on their domain, not just one. We may also decide to migrate older hardware based systems to a virtual machine on a case-by-case basis.

If you have any questions please contact support.