July 1, 2021 Release Notes

New features

Streamlined registration process

The registration process has been redesigned and will no longer require users to submit billing account information or complete their company profile.

screenshot of the first registration screen

Support user group Customer request

We have created a new user group labeled “Support.” Users in this group can perform troubleshooting actions such as disabling/enabling interfaces, toggling autonegotiation, and editing virtual circuits. Support users cannot perform any actions that have billing consequences (creating, upgrading, deleting services). They also cannot see admin and billing information in the portal.

For more information, see Groups and User Permissions.

screenshot of the groups with support highlighted

Concurrent sessions

You can now have up to 10 concurrent sessions. Previously, we only allowed one at a time. This meant that if you were performing actions using the API, you would be logged out of the portal. Similarly, if you logged in to the portal, you would need to re-authenticate your API session.

This change includes two new API calls:

  • GET /v2/auth/sessions – Returns a list of active session tokens with expiration date and IP address.

  • DELETE /v2/auth/sessions - Invalidate all active sessions.

To terminate an active portal session, log out or visit https://portal.packetfabric.com/auth/login.

Reseller Admin Portal customer and user management Customer request

Manage which users can access customer accounts

As of this release, only Admin users will see the full customer list. To allow a non-Admin user access to customer information, you can click Manage Users. This opens a panel where you can select a user and determine which group permissions they should have when viewing the customer’s account:

screenshot of the customers page with the view action highlighted

screenshot of the link user panel

For more information, see Manage Customers.

Add customers

With this release, you can now add customers directly. Previously, you could only invite customers to register an account.

screenshot of the link user panel

For more information, see Add or Invite Customers.

Resend invites

For customers whose invites are still pending, you can now resend the invite.

screenshot of the link user panel

Changes and enhancements

Marketplace-to-cloud capability for Microsoft Azure

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


  • The VC Request GET call now returns the following parameters:

    • rate_limit_in - The rate limit in from the request.
    • rate_limit_out - The rate limit out from the request.
    • allow_untagged_z - Whether the Z-side logical interface can be untagged.
  • GET /v2/services and GET /v2/services/{circuit_id} have a service_type parameter. Previously, this returned cloud for all cloud connections. It will now specify which type of cloud connection (e.g. cloud_hosted and cloud_dedicated).


  • We have added two new company types: Government and Not for Profit. Customer request

  • You can now filter the virtual circuit list by the types of cloud connections you are looking for. Previously, all cloud connections options were grouped together under “Cloud.”

    screenshot of the VC list

  • The ability to create a new billing account when placing an order has been extended to all services. Previously, this was only available when ordering a port.

Bug fixes

  • When selecting a marketplace provider as the Hosted cloud source, users should see the Displayed Company Name (if specified by the provider).
  • When creating a Hosted marketplace-to-cloud connection, the site/POP would improperly populate if you clicked the “Select Location” placeholder value in the locations drop-down menu.
  • Metrics graphs not factoring in user time zones.
  • Invalid zones accepted when provisioning AWS Hosted connections.
  • Team sign-up process was improperly allowing invites to be reused and was not updated when a signup was completed.
  • Users unable to delete Oracle Hosted cloud connections if the Oracle side had been deleted first.
  • Http 500 error with GET /v2/ports/{port_circuit_id}/router-logs.
Customer request = Indicates changes/features/fixes based on customer feedback.