Is Project44 down?
Last checked 2m agoNo incidents right now.
Project44 is operational right now. Last checked 2m ago; the most recent incident resolved 1d ago.
Real-time Project44 status, recent outages, and incident history — pulled directly from Project44's official status page at https://status.project44.com every 5 minutes. Pingoru tracks 139 Project44 services and has captured 63 incidents in the last 90 days (99.48% uptime). Get email, Slack, Discord, or webhook alerts the moment Project44 reports a new incident — free for 5 monitors, no credit card.
Recent outages & incidents
Past 90 days- Track & Trace Web Application (CTT)Sailing Schedules Web Application (CSS)Track & Trace Web Application (CTT)Sailing Schedules Web Application (CSS)Track & Trace APISailing Schedules APITrack & Trace APISailing Schedules APITrack & Trace EngineSailing Schedules Data Delivery (FTP)
Timeline · 3 updates
- investigating · Jul 27, 2026, 11:51 AM UTC
Dear Valued Customer, We are currently experiencing a delay in the processing of ocean shipment data. As a result, shipment updates in Movement may be delayed. During this time, the latest shipment data will continue to be available in CTT; however, shipment updates displayed in Movement may be delayed. Our engineering team is actively investigating the issue and working to restore normal service. As an organization, we remain committed to delivering reliable, high-availability services to our customers. If you have any questions or require further assistance, please feel free to contact us at [email protected]. Thank you for your patience and continued trust. Regards, Customer Support
- monitoring · Jul 27, 2026, 05:29 PM UTC
Dear Valued Customer, Our engineering team has identified the cause of the delay affecting ocean shipment data, and a resolution has been implemented. We are closely monitoring the system to ensure that services continue to operate as expected. We sincerely appreciate your patience and understanding as we work to resolve this issue. We will continue to keep you informed and provide updates as more information becomes available. As an organization, we remain committed to delivering reliable, high-availability services to our customers. If you have any questions or require further assistance, please feel free to contact us at [email protected]. Best Regards, Customer Support
- resolved · Jul 28, 2026, 10:06 AM UTC
Dear Valued Customer, The issue causing delays in the processing of ocean shipment data has been resolved. Our engineering team has confirmed that processing has returned to normal, and shipment updates are now flowing as expected in both Movement and CTT. We have verified that the affected services are operating normally. We sincerely apologize for any inconvenience this issue may have caused and appreciate your patience and understanding while we worked to resolve it. As an organization, we remain committed to delivering reliable, high-availability services to our customers. If you have any questions or require further assistance, please feel free to contact us at [email protected]. Thank you for your continued trust. Best Regards, Customer Support
Latest: Dear Valued Customer, The issue causing delays in the processing of ocean shipment data has been resolved. Our engineering team has confirmed that processing has returned to normal…
-
- NA - Movement
Timeline · 3 updates
- investigating · Jul 08, 2026, 06:12 PM UTC
Dear Valued Customer, We are currently investigating an issue affecting Movement in the NA Production environment. Some customers using specific internet service providers (ISPs) may be unable to log in to Movement. Our engineering team is actively investigating the issue and working to identify the root cause. We apologize for the inconvenience and appreciate your patience as we work to restore normal service. If you have any questions, please contact [email protected]. Best Regards, Customer Support Team
- identified · Jul 08, 2026, 08:01 PM UTC
Dear Valued Customer, We are continuing to investigate an issue affecting Movement in the NA Production environment. Based on our investigation, we have narrowed the issue to customers using Spectrum as their internet service provider (ISP), who may be unable to log in to Movement. We are actively working with Spectrum to help resolve the issue as quickly as possible. We apologize for the inconvenience and appreciate your patience as we work toward a resolution. If you have any questions, please contact [email protected]. Best Regards, Customer Support Team
- resolved · Jul 09, 2026, 03:22 PM UTC
Dear Valued Customer, The issue affecting Movement login in the NA Production environment has been resolved. Our investigation determined that the issue impacted some customers using specific internet service providers (ISPs). We have confirmed that affected users are now able to successfully log in to Movement, and service has been restored. We apologize for the inconvenience and appreciate your patience throughout this incident. If you continue to experience login issues, please contact **[[email protected]](mailto:[email protected])**. Best Regards, Customer Support Team
Latest: Dear Valued Customer, The issue affecting Movement login in the NA Production environment has been resolved. Our investigation determined that the issue impacted some customers usi…
-
- NA - Yard Management (YMS)NA - Appointment Manager
Timeline · 3 updates
- investigating · Jun 30, 2026, 07:53 PM UTC
Dear Valued Customer, We are currently experiencing an issue affecting Driver Text Messaging in Yard Management (YMS). Customers may experience delays or failures in outbound SMS notifications to drivers. As a result, driver text messages may remain in a pending state and not be delivered. Current Status: Our engineering team is actively investigating the issue and working to restore the service as quickly as possible. We apologize for the inconvenience and appreciate your patience while we work to resolve this issue. If you have any questions, please contact [email protected]. Best Regards, Customer Support Team
- monitoring · Jul 01, 2026, 12:28 PM UTC
Dear Valued Customer, Our Engineering team has implemented a fix for the Driver Text Messaging issue. The functionality is now operating normally, and we are actively monitoring the system to ensure continued stability. Regards, Customer Support Team
- resolved · Jul 02, 2026, 03:51 AM UTC
Dear Valued Customer, We are pleased to inform you that the issue affecting the Driver Text Messaging functionality has been fully resolved, and the service is now operating normally. Our engineering team identified the root cause of the issue and implemented the necessary corrective actions to restore full functionality. Users should now be able to send and receive driver text messages as expected without any further disruption. We sincerely apologize for any inconvenience this may have caused and greatly appreciate your patience and understanding throughout this incident. As an organization, we remain committed to providing reliable, high-availability services to our customers. If you have any questions or continue to experience any issues, please do not hesitate to contact us at [email protected]. Best Regards, Customer Support Team
Latest: Dear Valued Customer, We are pleased to inform you that the issue affecting the Driver Text Messaging functionality has been fully resolved, and the service is now operating normal…
-
- NA - DriveviewEU - Driveview
Timeline · 3 updates
- investigating · Jun 25, 2026, 05:19 PM UTC
Dear Valued Customer, We are currently investigating an issue affecting the Driveview App in the North America and Europe production environment, which is preventing drivers from starting tracking for shipments. The service is partially affected, and we are working to identify the root cause and restore full functionality as quickly as possible. At this time, shipment tracking initiation may be unavailable for some users. We appreciate your patience as we resolve this issue. As an organization, we are committed to providing reliable, high-availability services to our customers. If you have any questions, please don't hesitate to contact us at [email protected]. Best Regards Customer Support Team
- investigating · Jun 25, 2026, 05:20 PM UTC
We are continuing to investigate this issue.
- resolved · Jun 25, 2026, 05:45 PM UTC
Dear Valued Customer, The issue affecting the DriveView App in the North America and Europe production environments has been resolved. Our team has implemented the necessary fixes, and the service has been fully restored. Drivers should now be able to successfully start tracking for shipments, and shipment tracking initiation is functioning as expected. We sincerely appreciate your patience and understanding while we worked to resolve this issue. As an organization, we remain committed to providing reliable, high-availability services to our customers. If you continue to experience any issues or have any questions, please do not hesitate to contact us at [email protected]. Best Regards Customer Support Team
Latest: Dear Valued Customer, The issue affecting the DriveView App in the North America and Europe production environments has been resolved. Our team has implemented the necessary fixes,…
-
- Carrier Connections (Upstream Network)
Timeline · 2 updates
- identified · Jun 17, 2026, 07:52 PM UTC
Dear Valued Customer, Following the recent FedEx-mandated migration to webhook-based event delivery, project44 has identified several issues affecting a subset of Last Mile shipments. We are proactively sharing this to ensure full visibility into what we are tracking and where things stand. Action Required No action is required from customers at this time. Known Issues- • Missing Tracking Events — Some shipments are not receiving events after being subscribed to the webhook, causing them to appear stuck in a Scheduled or In Transit status. • Missing Event Location and/or UTC Offset — On some shipments, events are being received without location and/or UTC offset data. This is most commonly seen on the Delivered event and can impact delivery timestamp accuracy and downstream reporting or workflows that rely on this information. • Status Mapping Corrections — The webhook is introducing new exception codes that are not yet mapped in our system, causing some shipment exceptions to surface as standard In Transit events rather than being flagged correctly. • EDD Updating After Delivered Status — In a small number of cases, Estimated Delivery Dates (EDD) are updating after a Delivered event has already been received. project44 is actively working with FedEx technical support and our internal engineering team to investigate and resolve each of these items. We will provide updates as there are meaningful developments to share. We appreciate your understanding and patience during this period. At project44, we remain committed to delivering reliable, high-availability services to our customers. If you have any questions or concerns, please feel free to contact us at [email protected] Best regards, Customer Support Team project44
- resolved · Jul 23, 2026, 12:26 PM UTC
This incident has been resolved.
Latest: This incident has been resolved.
-
See the full Project44 outage history
6 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.
Browse Project44 outage history →Or sign up free to get alerts when Project44 breaks · 10 free monitors · No credit card
- Delay in Ocean Shipment Updates ResolvedStarted Jul 27, 2026, 11:51 AM UTC · Resolved Jul 28, 2026, 10:06 AM UTC · 22h 15m
- Started Jul 08, 2026, 06:12 PM UTC · Resolved Jul 09, 2026, 03:22 PM UTC · 21h 9m
- Started Jun 30, 2026, 07:53 PM UTC · Resolved Jul 02, 2026, 03:51 AM UTC · 1d 7h
- Started Jun 25, 2026, 05:19 PM UTC · Resolved Jun 25, 2026, 05:45 PM UTC · 25m
- Started Jun 17, 2026, 07:52 PM UTC · Resolved Jul 23, 2026, 12:26 PM UTC · 35d 16h
- Started May 18, 2026, 09:32 AM UTC · Resolved May 19, 2026, 11:23 AM UTC · 1d 1h
- CSS (Sailing Schedules) Unavailable ResolvedStarted May 08, 2026, 10:55 AM UTC · Resolved May 08, 2026, 12:14 PM UTC · 1h 19m
- Started May 08, 2026, 08:43 AM UTC · Resolved May 08, 2026, 09:42 AM UTC · 58m