October 26, 2021 Release Notes

New features

Import Cloud Router from a service provider (Beta)

You can now import the routes from a service provider’s Cloud Router into your existing Cloud Router. In this beta release, we are offering access to the PacketFabric Transit network and Salesforce.

screenshot of the Cloud Router import

EMEA support for Cloud Router

You can now provision Cloud Router connections from EMEA (Europe, Middle East, Africa) locations. We also support transregional connections between EMEA and North America.

Support for private customer POPs

Some customers might want to create their own sites/POPs on the PacketFabric network without that site being visible to other PacketFabric customers. We now support making certain POPs only visible to a specific customer.

For more information, contact your Implementation and Service Delivery Coordinator or email sales@packetfabric.com.

Changes and enhancements

Capacity tiers when creating a Cloud Router

When creating a new Cloud Router, you will now see options to select one or more regions and a capacity. These selections are used to determine the monthly price of the Cloud Router. Previously, all Cloud Routers had a flat fee regardless of how many connections they had.

The following capacities are available: 100 Mbps, 500 Mbps, 1 Gbps, 2 Gbps, 5 Gbps, 10 Gbps, 20 Gbps, 30 Gbps, 40 Gbps, 50 Gbps, 60 Gbps, 80 Gbps, 100 Gbps, and 100+ Gbps.

You can modify the regions and capacity at any time by editing the Cloud Router settings.

screenshot of the Cloud Router regions and capacity

Marketplace-to-cloud capability for Oracle Cloud Infrastructure

When creating a Hosted connection to Oracle Cloud Infrastructure, 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.

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


  • Added a confirmation dialog when deleting a capacity burst on a backbone virtual circuit.

  • When viewing the virtual circuit list in the portal, N/A (EPL mode) will appear under the VLAN column for EPL connections. Currently that space is empty for EPL connections.

  • Removed the Disconnected VCs page under port details.

  • Added a Cancel button to the Cloud Router provisioning workflow.

  • When provisioning a port, if a user selects a non-core location, they will now be required to select a checkbox confirming that they understand the SLA does not apply.

  • Users will now be prevented from deleting the last member in a LAG, and will instead see a message instructing them to delete the LAG (the remaining port will remain unaffected and be removed from the LAG).

  • When a Reseller Admin user completes the Add Customer action, they will no longer be required to create a user login for that customer. Instead, a user for that customer account can be added later (if necessary). Customer request

  • Removed the Connection Requests page from under Network. It now only appears under Marketplace.

  • A numbered alert will now appear next to Marketplace when a user has new connection requests:

    screenshot of the connection request alert

Bug fixes

  • New customer registration was failing in some instances.
  • Added support for 4-digit postal codes when adding contact information.
  • When ordering a Cloud Router connection, the Place Order action was not re-enabling after the user fixed a previous validation error.
  • Removed redundant ‘type’ field from the Cloud Router details page.
  • Changing the BGP authentication key for a Cloud Router connection was not updating the value as it should. Customer request
  • The portal was making unneccessary calls to the pricing API endpoint when users placed orders.
  • Activity logs were showing the wrong message when deleting a point-to-point connection.
  • subscription_term was missing in the response for GET /v2/services/cloud/connections/{cloud_circuit_id}.
  • A-side users were able to request third-party virtual circuits for inactive z-side ports.
  • If the A-side port is deleted, any outstanding IX connection requests are now also deleted.
  • Incorrect statistics were displayed in the Reseller Admin portal after a customer upgraded a port.

Knowledge base

New pages

Customer request = Indicates changes/features/fixes based on customer feedback.