Web and mobile optimization

IP Application Accelerator Traffic report

The IP Application Accelerator (IPA) presents traffic and bandwidth data associated with TCP application delivery through IPA. It delivers TCP/IP-based applications globally to users and lets you optimize the delivery of TCP/IP apps using ​Akamai​ dynamic mapping, route optimization, and packet redundancy features, and a high-performance transport protocol.

Data granularity
This report can show five-minute, hourly, or daily data intervals. Data is retained for up to 90 days.

Filters
Select at least one required filter in every report. For optional filters, making no selection returns all associated data for that filter.

  • SRIP slot data, or CP code (required). Content provider (CP) codes let you segment your delivered content for tracking and reporting purposes. All CP codes have ties to one or more services, which are tracked and reported under that CP code.

Metrics

  • Concurrent users. The number of concurrent connections, measured at five-minute intervals. A connection counts if the user is connected for any part of the five-minute period. For example, if User X disconnects at minute 2 and User Y connects at minute 4, this is considered two concurrent connections, so too if User X disconnects at minute 2 and reconnects at minute 4.

  • Peak concurrent users. The highest number of connections, measured at five-minute intervals. A connection counts if the user connects for any part of the five minute period.

  • Latest concurrent users. The most recent number of connections, measured at five-minute intervals. A connection counts if the user connects for any part of the five-minute period.

  • Throughput, in bits/sec. The rate of traffic from the client to the origin (incoming) and the rate of traffic to the client from the origin (outgoing), for origins that are served by associated SureRoute IP (SRIP) endpoints, converted into bits per second at five-minute intervals, based on connectivity from ​Akamai​ distributed network to edge nodes on your network.

  • Peak throughput, in bits/sec. The highest rate of traffic from the client to the origin (incoming) and the rate of traffic to the client from the origin (outgoing), converted into bits per second at five-minute intervals. Based on connectivity from ​Akamai​ distributed network to edge nodes on your network.

  • Latest throughput, in bits/sec. The most recent rate of traffic from the client to the origin (incoming) and the rate of traffic to the client from the origin (outgoing), converted into bits per second at five-minute intervals. Based on connectivity from ​Akamai​ distributed network to edge nodes on your network.

  • DNS requests over time. The number of DNS requests of any type that were made over time to process the various sessions associated with IPA traffic between served origin servers and clients.

  • Total DNS requests. The total number of DNS requests of any type made to process the various sessions associated with the IPA traffic between served origin servers and clients.

  • Peak DNS requests. The highest number of DNS requests of any type made to process the various sessions associated with IPA traffic to and from the Origin servers and clients that are being served.

  • Latest DNS requests. The most recent number of DNS requests of any type made to process the various sessions associated with the Session Accelerator traffic to and from the Origin servers and clients that are being served.

  • Total requests mapped to ​Akamai​. The total number of DNS requests that directed content to be retrieved from ​Akamai​ servers.

  • Peak DNS requests mapped to ​Akamai​. The highest number of DNS requests that directed content to be retrieved from ​Akamai​ servers.

  • Latest DNS requests mapped to ​Akamai​. The most recent number of DNS requests that directed content to be retrieved from ​Akamai​ servers.

  • Total requests mapped to origin. The total number of DNS requests mapped to retrieve content from an origin server.

  • Peak DNS requests mapped to origin. The highest number of DNS requests mapped to retrieve content from an origin server.

  • Latest DNS requests mapped to origin. The most recent number of DNS requests mapped to retrieve
    content from an origin server.

  • Total requests geo-mapped to origin. The total number of DNS requests serviced by the ​Akamai​ mapper network and directed to retrieve content from an origin server.

  • Peak DNS requests geo-mapped to origin. The highest number of DNS requests serviced by the ​Akamai​ mapper network and directed to retrieve content from an origin server.

  • Latest DNS requests geo-mapped to origin. The most recent number of DNS requests serviced by the ​Akamai​ mapper network and directed to retrieve content from an origin server.

What else is in play?
User sessions are comprised of traffic that is bidirectional between two SureRoute IP (SRIP) network endpoints. There's no difference between portions of the route and direction traffic flows.

Typically, a user opens a browser and makes a request of the origin server. The browser may open multiple TCP connections to process the session, but the request is a single session. User can open another browser window or application instance and make a subsequent request. When multiple instances are running separate requests, IP Application Accelerator considers them individual users. Sessions are HTTPS requests coupled with their responses.

IP Application Accelerator Blocked Traffic report

The IP Application Accelerator (IPA) Blocked Traffic report displays the amount of traffic blocked overall and the amount of traffic blocked for specific reasons, such as blacklisted IP addresses. IPA delivers TCP/IP-based applications to users on a global scale. IP Application Accelerator offers the versatility to optimize the delivery of a variety of TCP/IP applications using ​Akamai​ dynamic mapping, route optimization, and packet redundancy features, and a high-performance transport protocol.

Data granularity
This report can show five-minute, hourly, or daily data intervals. Data is retained for up to 90 days.

Filters
Select at least one required filter in every report. For optional filters, making no selection returns all associated data for that filter.

  • CP code (required). Content provider (CP) codes let you segment your delivered content for tracking and reporting purposes. All CP codes have ties to one or more services, which are tracked and reported under that CP code.

Metrics

  • Blocked volume by time. The volume in bytes of all traffic blocked for any reason over time.

  • Blacklist. The blocked volume in bytes of traffic from blacklisted IP addresses or CIDRs from Fast IP Blocking.

  • Geo blacklist. The blocked volume in bytes of traffic from blacklisted geographies (countries) from Fast IP Blocking.

  • Closed port. The blocked volume in bytes of traffic from packets dropped because the origin's port wasn't open (for example, port 22 traffic on a web server with only ports 80 and 443 open).

  • Unsupported protocols. The blocked volume in bytes of traffic from protocols blocked wholesale at the origin (for example, GRE traffic).

Session Accelerator (SXL) Traffic report

SXL product lets enterprises securely extend web-based applications to ​Akamai​ edge platform, bringing content close to end users. Performance improvements applied at the session level include route optimization, TCP optimization and packet replication techniques. The Session Accelerator Traffic report displays traffic data for an origin web server or a set of origins. You set the view on the Traffic page by selecting an account, a property, a context, and the associated contract. The context is the specific SXL pathway between two endpoints.

Data granularity
This report can show five-minute, hourly, or daily data intervals. Data is retained for up to 90 days.

Filters
Select at least one required filter in every report. For optional filters, making no selection returns all associated data for that filter.

  • SRIP slot data, or CP code (required). Content provider (CP) codes let you segment your delivered
    content for tracking and reporting purposes. All CP codes have ties to one or more services, which are tracked and reported under that CP code.

Metrics

  • Concurrent users. The number of concurrent connections, measured at five minute intervals. A connection counts if the user connects for any part of the five-minute period. For example, if User X disconnects at minute 2 and User Y connects at minute 4, this is considered two concurrent connections. So too if User X disconnects at minute 2 and reconnects at minute 4.

  • Peak concurrent users. The highest number of connections, measured at five minute intervals. A connection counts if the user connects for any part of the five-minute period.

  • Latest concurrent users. The most recent number of connections, measured at five-minute intervals. A connection counts if the user connects for any part of the five-minute period.

  • Throughput, in bits/sec. The rate of traffic from the client to the origin (incoming) and the rate of traffic to the client from the origin (outgoing), for origins served by associated SureRoute IP (SRIP) endpoints, converted into bits per second at five- minute intervals, based on connectivity from ​Akamai​ distributed network to edge nodes on your network.

  • Peak throughput, in bits/sec. The highest rate of traffic from the client to the origin (incoming) and the rate of traffic to the client from the origin (outgoing), converted into bits per second at five-minute intervals. Based on connectivity from ​Akamai​ distributed network to edge nodes on your network.

  • Latest throughput, in bits/sec. The most recent rate of traffic from the client to the origin (incoming) and the rate of traffic to the client from the origin (outgoing), converted into bits per second at five-minute intervals. Based on connectivity from ​Akamai​ distributed network to edge nodes on your network.

  • DNS requests over time. The number of DNS requests of any type that were made as a function of time to process the various sessions associated with the IPA traffic to and from origin servers and clients being served.

  • Total DNS requests. The total number of DNS requests of any type that were made to process the various sessions associated with IPA traffic to and from origin servers and clients being served.

  • Peak DNS requests. The highest number of DNS requests of any type made to process the various sessions associated with IPA traffic between served origin servers and clients.

  • Latest DNS requests. The most recent number of DNS requests of any type made to process the various sessions associated with the Session Accelerator traffic between served origin servers and clients.

  • Total requests mapped to ​Akamai​. The total number of DNS requests that directed content to be retrieved from ​Akamai​ servers.

  • Peak DNS requests mapped to ​Akamai​. The highest number of DNS requests that directed content to be retrieved from ​Akamai​ servers.

  • Latest DNS requests mapped to ​Akamai​. The most recent number of DNS requests that directed content to be retrieved from ​Akamai​ servers.

  • Total requests mapped to origin. The total number of DNS requests mapped to retrieve content from an origin server.

  • Peak DNS requests mapped to origin. The highest number of DNS requests mapped to retrieve content
    from an origin server.

  • Latest DNS requests mapped to origin. The most recent number of DNS requests mapped to retrieve
    content from an origin server.

  • Total requests geo-mapped to origin. The total number of DNS requests serviced by the ​Akamai​ mapper network and directed to retrieve content from an origin server.

  • Peak DNS requests geo-mapped to origin. The highest number of DNS requests serviced by the ​Akamai​ mapper network and directed to retrieve content from an origin server.

  • Latest DNS requests geo-mapped to origin. The most recent number of DNS requests serviced by the ​Akamai​ mapper network and directed to retrieve content from an origin server.

What else is in play?
Sessions are comprised of traffic that is bidirectional between two SureRoute IP (SRIP) network endpoints. There's no difference between portions of the route and direction traffic flows.

Typically, a user opens a browser and makes a request of the origin server. The browser may open multiple TCP connections to process the session, but the request is a single session. User can open another browser window or application instance and make a subsequent request. When multiple instances are running separate requests IP Application Accelerator considers them individual users. Sessions are HTTPS requests coupled with their responses.

Session Accelerator (SXL) Blocked Traffic report

SXL product lets enterprises securely extend their web-based applications to the edge network, bringing content close to end users. Performance improvements applied at the session level include route optimization, TCP optimization and packet replication techniques. Session Accelerator Blocked Traffic report displays the amount of traffic blocked overall and the amount of traffic blocked for specific reasons, such as blacklisted IP addresses.

Data granularity
This report can show five-minute, hourly, or daily data intervals. Data is retained for up to 90 days.

Filters
Select at least one required filter in every report. For optional filters, making no selection returns all associated data for that filter.

  • CP code (required). Content provider (CP) codes let you segment your delivered content for tracking and reporting purposes. All CP codes have ties to one or more services, which are tracked and reported under that CP code.

Metrics

  • Blocked volume by time. The volume in bytes of all traffic blocked for any reason over time.

  • Blacklist . The blocked volume in bytes of traffic from blacklisted IP addresses or CIDRs from Fast IP Blocking.

  • Geo blacklist. The blocked volume in bytes of traffic from blacklisted geographies (countries) from Fast IP Blocking.

  • Closed port. The blocked volume in bytes of traffic from packets dropped because the port is not open on the origin (for example, port 22 traffic on a web server with only ports 80 and 443 open).

  • Unsupported protocols. The blocked volume in bytes of traffic from protocols that are blocked wholesale at the origin (for example, GRE traffic).

Cloudlets Usage report

The Cloudlets Usage, or Cloudlets Activity report provides metrics for Cloudlets based on selected traffic segments. You can choose to view the data for one or more Cloudlet types. These usage metrics include the number of times a Cloudlet ran in response to either an incoming request or a rule match.

Filters

  • Traffic segments, or CP code (required). Content provider (CP) codes let you segment your delivered
    content for tracking and reporting purposes. All CP codes have ties to one or more services, which are tracked and reported under that CP code.

  • Cloudlet type. The type of Cloudlets that you want to see data for. Optional: selecting nothing returns data for all Cloudlet types you may have.

Metrics

  • Cloudlets traffic. The total number of match hits and misses for the selected Cloudlets types.

  • Max cloudlets traffic. The highest number of match hits and misses for the selected Cloudlets types.

  • Latest cloudlets traffic. The most recent number of match hits and misses for the selected Cloudlets types.

  • Match hits. The total number of times a Cloudlet ran in response to an incoming request or after a rule within a policy matched.

  • Max match hits. The highest number of times a Cloudlet ran in response to an incoming request or after a rule within a policy matched.

  • Latest match hits. The most recent number of times a Cloudlet ran in response to an incoming request or after a rule within a policy matched.


Did this page help you?