June 17, 2021 Release Notes

Changes and enhancements

Marketplace-to-cloud capability for Google Cloud

When creating a Hosted connection to Google Cloud Platform, you now have the option to extend that connection to a marketplace member:

screenshot of the marketplace source option

When you click this link, you will see options to select a marketplace member and location:

screenshot of the marketplace source menus

For more information, see Marketplace-to-Cloud Connections.

NAT-capable device selection for Cloud Router

Portal support for Cloud Router NAT functionality is still in progress and will be made available in a future release. In the meantime, we are allowing customers to forecast their intentions to use NAT over Cloud Router. Selecting this checkbox ensures your connections are optimized for NAT.

nat checkbox

Highlight weekends and work hours in graphs

Statistical graphs now include options to highlight weekends (Saturday, Sunday) and work hours (9 a.m. to 5 p.m.).

The work hours highlight is available when displaying data within the last 2 days:

work hour highlight

The weekend highlight is available when displaying data that is more than 2 days but less than 14:

weekend highlight


  • Added a new request_type property to the payload returned by /v2/services/requests. This will be used to indicate what type of virtual circuit request it is. This will be used to support our marketplace-to-cloud connections and future development.
  • Added additional information about the requester to the /v2/services/requests response.
  • Removed unnecessary fields from the /v2/ports response.


  • Improved point-to-point provisioning time.
  • Currently, if we don’t have a value for the interface module, we put “Unknown.” This has caused confusion for some customers when viewing the port details page. In the future that field will simply be hidden.

Bug fixes

  • Reseller Admin Portal - Updating contact information without uploading a document would result in an error.
  • Selecting an untagged VLAN ID when creating a dedicated port connection on a Cloud Router would result in an error.
  • The width of the progress bar shown when provisioning or deleting a service was not accurately representing the percentage complete.
  • The sidebar service count for virtual circuits was improperly including Cloud Router connections.
  • API was improperly accepting a speed parameter for the call to upgrade a Dedicated cloud port.
  • API POST requests for Azure should not include a pop parameter.
  • Removed type parameter from API /v2/locations documentation. It is not supported.

Knowledge base

New pages