During customer network endpoint reviews, questions often arise regarding external endpoints accessed by IBSS applications. This article explains the purpose of commonly observed endpoints and identifies connections that may indicate a configuration issue.
Common External Endpoints
ipinfo.io
Purpose:
Used to determine a device's public IP address and related network information.
Use Cases:
- Identifying the public IP used for internet access.
- Retrieving geolocation-related information such as region or timezone.
- Supporting diagnostics and network-aware functionality.
Expected Behaviour:
- Connections to ipinfo.io may be observed from IBSS deployments and are considered normal.
google.com
Purpose:
Used as a basic internet connectivity check.
Use Cases:
- Verifying outbound internet access.
- Confirming general network connectivity.
Expected Behaviour:
Occasional connections to google.com may be observed and are considered normal for connectivity validation.
*.blob.core.windows.net
Purpose:
Used to retrieve Map/Image SVGs stored in the Azure Blob storage CDN.
Use Cases:
- Media files used by the IBSS Applications
Expected behaviour
All media should come from the domain - storage.ibss.customer.iconics.cloud. However, on occasions, while testing media files updates, it may be possible that the media reference is pointed directly to the blob storage endpoint.