The BreadCrumbs response

The BreadCrumbs response header that's sent to a player consists various sub-fields of data.

Sub-field key Sub-field value Additional info
b <Request ID> A unique identifier assigned to the request. (This helps Akamai support teams quickly pull the relevant log line associated with the request.)
a <Component IP> The IP address of the node/host currently processing the request. This can be an edge server or an origin.
Note: If the node or host is not either of these two types, it's excluded.
c <Component Letter> This is a single letter identifier for the Akamai network component that was involved during that phase of the request. (Your Akamai representative can use this value to determine where in the request phase the BreadCrumb was gathered.)
n <Component Geo> Geographic details associated with the node/host currently processing the request.
o <Component ASN> The autonomous system number associated with the current node/host.

Example 1: When served from within Akamai

In this example, the request flow is Edge to Peer, so the BreadCrumbs format would be: [<component-ip>,<request-id>,<component-letter>,<component-geo>,<component-asn>],[<component-letter>,<component-geo>,<component-asn>]:

[a=12.34.567.89,b=12345678,c=g,n=US_CA_SANJOSE,o=20940],[c=p,n=US_CA_SANJOSE,o=55155]

Example 2: When served from an origin

In this example, the request flow is Edge to Cache to Origin, so the BreadCrumbs format would be: [<component-ip>,<request-id>,<component-letter>,<component-geo>,<component-asn>,[<component-letter>,<component-geo>,<component-asn>],[<component-ip>,<component-letter>]:

[a=12.34.567.89,b=12345678,c=g,n=US_CA_SANJOSE,o=20940],[c=c,n=US_CA_SANJOSE,o=55155],[a=987.654.321.09,c=o]