In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Apr 03, 2026 - 16:40 UTC
Apr 03, 2026 - 16:40 UTC
Scheduled - Upcoming Change: J.B. Hunt Capacity Provider Split
Effective Date: April 16, 2026, at 12:00 AM CST
Action Required: Review your integrations and workflows before the effective date.
What's Changing
To support all product capabilities across J.B. Hunt's three main divisions, project44 is
separating the existing J B Hunt Transport Inc capacity provider into three distinct
records — one per operating division. This change is required to support new TMS
products and capabilities, and will go into effect on April 16, 2026, at 12:00 AM CST.
J B HUNT TRANSPORT INC
• Primary SCAC: HJBT
• Secondary SCACs: HDRF, HIRF, HJBH, HJBL, HJBO, HLTB, HREV, XJLW
• DOT: 80806
• MC: 135797
• Master Carrier ID: BCPTUMXQ
J B HUNT TRANSPORT INC (INTERMODAL DIVISION)
• Primary SCAC: HJBI
• Master Carrier ID: L7LKKI65
• HJBI was previously nested under J B Hunt Transport Inc
J B HUNT TRANSPORT INC (BROKERAGE DIVISION)
• Primary SCAC: HJBB
• Master Carrier ID: MLZR3EVK
• HJBB was previously nested under J B Hunt Transport Inc
Tracking Impact
No tracking disruption. project44 deploys a single J.B. Hunt API tracking user that is
already attached to all three capacity providers. Active and existing shipments will
continue to receive tracking updates without interruption regardless of which SCAC is
used.
What This Means for You
Starting April 16, 2026, at 12:00 AM CST, any shipment created using HJBI or HJBB
will be associated with the new division-level capacity provider — not the original J B
Hunt Transport Inc record. Shipments created before April 16 are not affected and will
retain their current carrier association.
This affects:
• The carrier name returned in API responses
• Carrier attribution in analytics and reporting
• Webhook payloads that include carrier name
• Any internal process or system that references the carrier by name
Your Options — What to Do Before April 16
Different customers have built different workflows. Here are the most common
scenarios and what we recommend for each.
Scenario 1: You create intermodal shipments using HJBI and don't want to
update your systems
Switch to using HJBT for those shipments before April 16, 2026, at 12:00 AM CST.
HJBT will remain on the original J B Hunt Transport Inc capacity provider, and your
carrier name references will be unaffected. Tracking will not be impacted. That said, we
recommend routing shipments under the correct division SCAC where possible.
Scenario 2: You create brokerage shipments using HJBB and don't want to
update your systems
Same approach — route those shipments under HJBT before April 16, 2026, at 12:00
AM CST to avoid any carrier name changes downstream. Tracking will not be impacted.
That said, we recommend routing shipments under the correct division SCAC where
possible.
Scenario 3: You're fine updating your systems
Update any hardcoded carrier name references from J B Hunt Transport Inc to the
appropriate division name — J B Hunt Transport Inc (Intermodal Division) or J B Hunt
Transport Inc (Brokerage Division) — before April 16, 2026, at 12:00 AM CST.
Scenario 4: You use webhooks or API callbacks that include carrier name
Audit your webhook consumers and API integrations. After April 16, 2026, at 12:00 AM
CST, the carrier name field for HJBI and HJBB shipments will reflect the new division-
level names. Update any downstream logic that matches or filters on carrier name.
Scenario 5: You have internal reporting or dashboards built on carrier name
Shipments created after April 16, 2026, at 12:00 AM CST using HJBI or HJBB will
appear under the new capacity provider names. If you need historical and future data to
align under one name, plan that mapping in your reporting layer.
Timeline
• Now: Review this article and assess impact on your workflows.
• Before April 16, 2026, at 12:00 AM CST: Make any necessary updates to
integrations, routing rules, or SCAC usage.
• April 16, 2026, at 12:00 AM CST: Change goes live — new capacity providers
become active.
• After April 16, 2026: Shipments using HJBI or HJBB map to their respective
division records automatically.
Questions? Contact support@project44.com or reach out to your account team before the effective date.
Apr 3, 2026 16:40 - Apr 16, 2026 06:23 UTC
Effective Date: April 16, 2026, at 12:00 AM CST
Action Required: Review your integrations and workflows before the effective date.
What's Changing
To support all product capabilities across J.B. Hunt's three main divisions, project44 is
separating the existing J B Hunt Transport Inc capacity provider into three distinct
records — one per operating division. This change is required to support new TMS
products and capabilities, and will go into effect on April 16, 2026, at 12:00 AM CST.
J B HUNT TRANSPORT INC
• Primary SCAC: HJBT
• Secondary SCACs: HDRF, HIRF, HJBH, HJBL, HJBO, HLTB, HREV, XJLW
• DOT: 80806
• MC: 135797
• Master Carrier ID: BCPTUMXQ
J B HUNT TRANSPORT INC (INTERMODAL DIVISION)
• Primary SCAC: HJBI
• Master Carrier ID: L7LKKI65
• HJBI was previously nested under J B Hunt Transport Inc
J B HUNT TRANSPORT INC (BROKERAGE DIVISION)
• Primary SCAC: HJBB
• Master Carrier ID: MLZR3EVK
• HJBB was previously nested under J B Hunt Transport Inc
Tracking Impact
No tracking disruption. project44 deploys a single J.B. Hunt API tracking user that is
already attached to all three capacity providers. Active and existing shipments will
continue to receive tracking updates without interruption regardless of which SCAC is
used.
What This Means for You
Starting April 16, 2026, at 12:00 AM CST, any shipment created using HJBI or HJBB
will be associated with the new division-level capacity provider — not the original J B
Hunt Transport Inc record. Shipments created before April 16 are not affected and will
retain their current carrier association.
This affects:
• The carrier name returned in API responses
• Carrier attribution in analytics and reporting
• Webhook payloads that include carrier name
• Any internal process or system that references the carrier by name
Your Options — What to Do Before April 16
Different customers have built different workflows. Here are the most common
scenarios and what we recommend for each.
Scenario 1: You create intermodal shipments using HJBI and don't want to
update your systems
Switch to using HJBT for those shipments before April 16, 2026, at 12:00 AM CST.
HJBT will remain on the original J B Hunt Transport Inc capacity provider, and your
carrier name references will be unaffected. Tracking will not be impacted. That said, we
recommend routing shipments under the correct division SCAC where possible.
Scenario 2: You create brokerage shipments using HJBB and don't want to
update your systems
Same approach — route those shipments under HJBT before April 16, 2026, at 12:00
AM CST to avoid any carrier name changes downstream. Tracking will not be impacted.
That said, we recommend routing shipments under the correct division SCAC where
possible.
Scenario 3: You're fine updating your systems
Update any hardcoded carrier name references from J B Hunt Transport Inc to the
appropriate division name — J B Hunt Transport Inc (Intermodal Division) or J B Hunt
Transport Inc (Brokerage Division) — before April 16, 2026, at 12:00 AM CST.
Scenario 4: You use webhooks or API callbacks that include carrier name
Audit your webhook consumers and API integrations. After April 16, 2026, at 12:00 AM
CST, the carrier name field for HJBI and HJBB shipments will reflect the new division-
level names. Update any downstream logic that matches or filters on carrier name.
Scenario 5: You have internal reporting or dashboards built on carrier name
Shipments created after April 16, 2026, at 12:00 AM CST using HJBI or HJBB will
appear under the new capacity provider names. If you need historical and future data to
align under one name, plan that mapping in your reporting layer.
Timeline
• Now: Review this article and assess impact on your workflows.
• Before April 16, 2026, at 12:00 AM CST: Make any necessary updates to
integrations, routing rules, or SCAC usage.
• April 16, 2026, at 12:00 AM CST: Change goes live — new capacity providers
become active.
• After April 16, 2026: Shipments using HJBI or HJBB map to their respective
division records automatically.
Questions? Contact support@project44.com or reach out to your account team before the effective date.
Apr 3, 2026 16:40 - Apr 16, 2026 06:23 UTC
About This Site
Check here for updates about project44's API service availability. Subscribe to receive real-time incident, maintenance, and downtime updates by email, text, or RSS.
NA - Movement
Under Maintenance
NA - Visibility Operations Center (VOC)
Under Maintenance
NA - Network Management Center (NMC)
Operational
NA - Carrier VOC
Operational
NA - Driveview
Operational
NA - Inventory
Operational
NA - Orders
Operational
NA - Yard Management (YMS)
Operational
NA - Appointment Manager
Operational
NA - Sandbox
Operational
NA - LTL
Operational
Visibility Operations Center (VOC)
Operational
Dispatch API
Operational
Documents API
Operational
Rating API
Operational
Tracking API
Operational
NA - Truckload
Under Maintenance
Visibility Operations Center (VOC)
Operational
Network Management Center (NMC)
Operational
Documents API
Operational
Rating API
Operational
Tendering API
Operational
Tracking API
Under Maintenance
Carrier VOC
Operational
Analytics
Under Maintenance
Booking API
Operational
NA - Parcel
Operational
Visibility Operations Center (VOC)
Operational
Documents API
Operational
Tracking API
Operational
NA - Ocean
Operational
Visibility Operations Center (VOC)
Operational
Tracking API
Operational
Analytics
Operational
Port Intel
Operational
Extended Visibility (Door to Door)
Operational
Terminal Visiblity
Operational
Tendering API
Operational
Booking API
Operational
NA - Rail
Operational
Visibility Operations Center (VOC)
Operational
Tracking API
Operational
Asset Tracking
Operational
Shipment Tracking API
Operational
NA - Air
Operational
Visibility Operations Center (VOC)
Operational
Tracking API
Operational
NA - Container Track & Trace (CTT)
Operational
Track & Trace Web Application (CTT)
Operational
Track & Trace API
Operational
Track & Trace Engine
Operational
NA - Container Sailing Schedules (CSS)
Operational
Sailing Schedules Web Application (CSS)
Operational
Sailing Schedules API
Operational
Sailing Schedules Data Delivery (FTP)
Operational
Sailing Schedules Engine
Operational
NA - Last Mile
Operational
Data API
Operational
Orders API
Operational
Shipments API
Operational
Case Service API
Operational
Tracking Page
Operational
Application
Operational
Convey Website
Operational
Carrier Connections (Upstream Network)
Operational
Processing
Operational
SFTP
Operational
Data Ingestion
Operational
Predictive Delivery Date API
Operational
UOV API
Operational
EU - Movement
Operational
EU - Visibility Operations Center (VOC)
Operational
EU - Network Management Center (NMC)
Operational
EU - Carrier VOC
Operational
EU - Driveview
Operational
EU - Inventory
Operational
EU - Orders
Operational
EU - Yard Management (YMS)
Operational
EU - Appointment Manager
Operational
EU - Sandbox
Operational
EU - LTL
Operational
Visibility Operations Center (VOC)
Operational
Dispatch API
Operational
Documents API
Operational
Rating API
Operational
Tracking API
Operational
EU - Parcel
Operational
Visibility Operations Center (VOC)
Operational
Documents API
Operational
Tracking API
Operational
EU - Truckload
Operational
Visibility Operations Center (VOC)
Operational
Network Management Center (NMC)
Operational
Documents API
Operational
Rating API
Operational
Tendering API
Operational
Tracking API
Operational
Carrier VOC
Operational
Analytics
Operational
Booking API
Operational
EU - Ocean
Operational
Visibility Operations Center (VOC)
Operational
Tracking API
Operational
Analytics
Operational
Port Intel
Operational
Extended Visibility (Door to Door)
Operational
Terminal Visiblity
Operational
Booking API
Operational
Tendering API
Operational
EU - Rail
Operational
Visibility Operations Center (VOC)
Operational
Tracking API
Operational
Asset Tracking
Operational
Shipment Tracking API
Operational
EU - Air
Operational
Visibility Operations Center (VOC)
Operational
Tracking API
Operational
EU - Container Track & Trace (CTT)
Operational
Track & Trace Web Application (CTT)
Operational
Track & Trace API
Operational
Track & Trace Engine
Operational
EU - Container Sailing Schedules (CSS)
Operational
Sailing Schedules Web Application (CSS)
Operational
Sailing Schedules API
Operational
Sailing Schedules Data Delivery (FTP)
Operational
Sailing Schedules Engine
Operational
EU - Last Mile
Operational
Data API
Operational
Orders API
Operational
Shipments API
Operational
Case Service API
Operational
Tracking Page
Operational
Application
Operational
Convey Website
Operational
Carrier Connections (Upstream Network)
Operational
Processing
Operational
SFTP
Operational
Data Ingestion
Operational
UOV API
Operational
Developer Portal
Operational
Upstream Network Providers
Under Maintenance
LTL Carrier
Operational
TL Carrier/ELD
Under Maintenance
Parcel Carrier
Operational
Ocean Carrier
Operational
Rail Carrier
Operational
Air Carrier
Operational
NA - Flat File Upload (POV Manager)
Operational
Shipment Creation/Update
Operational
Shipment Tracking
Operational
EU - Flat File Upload (POV Manager)
Operational
Shipment Creation/Update
Operational
Shipment Tracking
Operational
YMS
Operational
Appointment Manager
Operational
Yard Visibility
Operational
YMS External API
Operational
AI Disruption Navigator
Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.
Scheduled Maintenance
CMA CGM Digital Factory - Scheduled Maintenance Apr 4, 2026 12:00-17:00 UTC
Dear Valued Customer,
CMA CGM has informed us of scheduled system maintenance, during which API access will be temporarily unavailable. As a result, there may be delays in receiving events. We appreciate your understanding and patience during this time.
The current planned time frame is as follows:
Maintenance start: 04th of April 2026, 12:00 PM UTC
Maintenance end: 04th of April 2026, 05:00 PM UTC
Best Regards
Customer Support
Posted on Apr 03, 2026 - 18:01 UTC
CMA CGM has informed us of scheduled system maintenance, during which API access will be temporarily unavailable. As a result, there may be delays in receiving events. We appreciate your understanding and patience during this time.
The current planned time frame is as follows:
Maintenance start: 04th of April 2026, 12:00 PM UTC
Maintenance end: 04th of April 2026, 05:00 PM UTC
Best Regards
Customer Support
Posted on Apr 03, 2026 - 18:01 UTC
Kintetsu World Express(KWE) EDI System Maintenence Apr 12, 2026 13:00-18:00 UTC
Dear valued Customer,
We have been informed about the scheduled maintenance of the Kintetsu World Express (KWE) EDI Production System. All Inbound & Outbound EDI file transmissions systems will be unavailable during the maintenance window.
Maintenance Start: 12th April 2026, 13:00 UTC
Maintenance End: 12th April 2026, 18:00 UTC
As an organization, we are committed to providing reliable and high-availability service to our customers. In case of any questions, please do not hesitate to reach out to support@project44.com.
Best regards,
Engineer, Customer Support Operations
Posted on Mar 20, 2026 - 03:19 UTC
We have been informed about the scheduled maintenance of the Kintetsu World Express (KWE) EDI Production System. All Inbound & Outbound EDI file transmissions systems will be unavailable during the maintenance window.
Maintenance Start: 12th April 2026, 13:00 UTC
Maintenance End: 12th April 2026, 18:00 UTC
As an organization, we are committed to providing reliable and high-availability service to our customers. In case of any questions, please do not hesitate to reach out to support@project44.com.
Best regards,
Engineer, Customer Support Operations
Posted on Mar 20, 2026 - 03:19 UTC