View categories

Categories

Heroku Architecture
- Compute (Dynos)
  - Dyno Management
  - Dyno Concepts
  - Dyno Behavior
  - Dyno Reference
  - Dyno Troubleshooting
- Stacks (operating system images)
- Networking & DNS
- Platform Policies
- Buildpacks
- Platform Principles

Developer Tools
- Command Line
- Heroku VS Code Extension

Deployment
- Deploying with Git
- Deploying with Docker
- Deployment Integrations

Continuous Delivery & Integration (Heroku Flow)
- Continuous Integration

Language Support
- Node.js
  - Troubleshooting Node.js Apps
  - Node.js Behavior in Heroku
  - Working with Node.js
- Ruby
  - Rails Support
  - Working with Bundler
  - Working with Ruby
  - Ruby Behavior in Heroku
  - Troubleshooting Ruby Apps
- Python
  - Working with Python
  - Background Jobs in Python
  - Python Behavior in Heroku
  - Working with Django
- Java
  - Java Behavior in Heroku
  - Working with Java
  - Working with Maven
  - Working with Spring Boot
  - Troubleshooting Java Apps
- PHP
  - Working with PHP
  - PHP Behavior in Heroku
- Go
  - Go Dependency Management
- Scala
- Clojure
- .NET
  - Working with .NET

Databases & Data Management
- Heroku Postgres
  - Postgres Basics
  - Postgres Getting Started
  - Postgres Performance
  - Postgres Data Transfer & Preservation
  - Postgres Availability
  - Postgres Special Topics
  - Migrating to Heroku Postgres
- Heroku Key-Value Store
- Apache Kafka on Heroku
- Other Data Stores

AI
- Working with AI
- Heroku Inference
  - Heroku Inference Quick Start Guides
  - Inference API
  - Inference Essentials
  - AI Models
- Tool Use
- Vector Database
- AI Integrations

Monitoring & Metrics
- Logging

App Performance

Add-ons
- All Add-ons

Collaboration

Security
- App Security
- Identities & Authentication
  - Single Sign-on (SSO)
- Private Spaces
  - Infrastructure Networking
- Compliance

Heroku Enterprise
- Enterprise Accounts
- Enterprise Teams

Patterns & Best Practices

Extending Heroku
- Platform API
- App Webhooks
- Heroku Labs
- Building Add-ons
  - Add-on Development Tasks
  - Add-on APIs
  - Add-on Guidelines & Requirements
- Building CLI Plugins
- Developing Buildpacks
- Dev Center

Accounts & Billing

Troubleshooting & Support

Integrating with Salesforce
- Heroku AppLink
  - Getting Started with Heroku AppLink
  - Heroku AppLink Reference
  - Working with Heroku AppLink
- Heroku Connect (Salesforce sync)
  - Heroku Connect Administration
  - Heroku Connect Reference
  - Heroku Connect Troubleshooting
- Other Salesforce Integrations

Dyno System Clock Synchronization

Last updated October 16, 2024

Dynos use the Network Time Protocol (NTP) for time synchronization indirectly via kernel passthrough. We configure the dyno’s underlying host to use time services provided by the Heroku platform’s Stratum 2 NTP servers. These servers sync to a pool of Stratum 1 time servers provided by NIST. Heroku uses the same time servers across its entire fleet to ensure homogeneous and synchronous time regardless of location.

Keep reading

Dyno Behavior

Feedback

Log in to submit feedback.

Rolling Deploys Networking