Using Sockets

Sockets are only available for paid apps, and traffic from sockets is billed as outgoing bandwidth. Sockets are also limited by daily and per minute (burst) quotas. App Engine supports outbound sockets through the appengine/socket package.

Libraries that can accept a net.Conn should work without modification.

Limitations and restrictions

Although App Engine supports sockets, there are certain limitations and behaviors you need to be aware of when using sockets:

  • Sockets are available only for paid apps.
  • You cannot create a listen socket; you can only create outbound sockets.
  • FTP is not supported.
  • You can only use TCP or UDP; arbitrary protocols are not allowed.
  • You cannot bind to specific IP addresses or ports.
  • Port 25 (SMTP) is blocked; you can still use authenticated SMTP on the submission port 587.
  • Private, broadcast, multicast, and Google IP ranges (except those whitelisted below), are blocked:

    • Google Public DNS:,, 2001:4860:4860::8888, 2001:4860:4860::8844 port 53
    • Gmail SMTPS: port 465 and 587
    • Gmail POP3S: port 995
    • Gmail IMAPS: port 993
  • Socket descriptors are associated with the App Engine app that created them and are non-transferable (cannot be used by other apps).

  • Sockets may be reclaimed after 2 minutes of inactivity; any socket operation keeps the socket alive for a further 2 minutes.

Using sockets with the development server

You can run and test code using sockets on the development server, without using any special command line parameters.

App Engine sample using sockets

For a sample using sockets, see the socket demo app in the Google Cloud Platform GitHub.

Send feedback about...

App Engine standard environment for Go