This media is not supported in your browser
VIEW IN TELEGRAM
There were some changes to loadboard, if youβre experiencing an issue related to Load detailed view update the extension as per video. Latest version as of now 3.17.7
We apologize for the inconvenience it mightβve caused.
We apologize for the inconvenience it mightβve caused.
π4
This media is not supported in your browser
VIEW IN TELEGRAM
π Tired of waiting for Relay AI Assistant to shake? LoadFetcher's AI tags show you instantly bookable loads! Join 4000+ dispatchers working smarter, not harder. #LoadFetcher #TruckingTech
π₯3β‘1
This media is not supported in your browser
VIEW IN TELEGRAM
π Ever dealt with loads that have impossible delivery times?
LoadFetcher flags these time-wasters, so you can save money on remove services!
#freightbroker #logistics #trucking #dispatch #loadboard #freighttech
LoadFetcher flags these time-wasters, so you can save money on remove services!
#freightbroker #logistics #trucking #dispatch #loadboard #freighttech
π₯4π3π1
Important update: The LoadFetcher Chrome extension's refresh feature was temporarily affected by recent changes to the Relay Loadboard. The issue has been resolved. For the quickest fix, simply remove and reinstall the extension. Thank you for your patience!
Download the latest version by cliking this link: https://chromewebstore.google.com/detail/loadfetcher-relay-amazon/ihcgicdogclbieclnldfjmlglkolankb
Download the latest version by cliking this link: https://chromewebstore.google.com/detail/loadfetcher-relay-amazon/ihcgicdogclbieclnldfjmlglkolankb
Google
LoadFetcher - Relay Amazon Efficiency Booster - Chrome Web Store
Dispatch Workflow Automation, Post Truck Manager, Refresher and many more for Relay Amazon Loadboard.
This media is not supported in your browser
VIEW IN TELEGRAM
π LoadFetcher keeps your score high.
β‘ On-Page Notifications β see alerts right inside Amazon Relay.
β° ETA Heads-Up β avoid being late to delivery by catching issues an hour early.
π Checkout Alerts β remind drivers to check out on time, avoid penalties.
Stay ahead. Keep your performance score high.
π Download LoadFetcher today.
https://loadfetcher.com
https://t.me/loadfetcher
β‘ On-Page Notifications β see alerts right inside Amazon Relay.
β° ETA Heads-Up β avoid being late to delivery by catching issues an hour early.
π Checkout Alerts β remind drivers to check out on time, avoid penalties.
Stay ahead. Keep your performance score high.
π Download LoadFetcher today.
https://loadfetcher.com
https://t.me/loadfetcher
1π6π2β€1
This media is not supported in your browser
VIEW IN TELEGRAM
ππ’ Dispatcher vs Driver β arguments about late loads are stressful.
But with LoadFetcher Notifications, no more guessing π
β Real-time updates
β On-time alerts
β Less shouting, more driving
π Make logistics smoother, faster, and stress-free π₯
π Download LoadFetcher today.
https://loadfetcher.com
https://t.me/loadfetcher
But with LoadFetcher Notifications, no more guessing π
β Real-time updates
β On-time alerts
β Less shouting, more driving
π Make logistics smoother, faster, and stress-free π₯
π Download LoadFetcher today.
https://loadfetcher.com
https://t.me/loadfetcher
β‘4π4π1
π Introducing the New Plan β Only $24/month!
Everything in Free, plus:
β Extension to 5 devices/browsers
β Financials & driver earnings
β In-page trip notifications
β Detailed load view & analytics
β Quick βPost a Truckβ creation
β¦and many more features to grow your operations!
Upgrade today and take your workflow to the next level. πΌβ¨
Everything in Free, plus:
β Extension to 5 devices/browsers
β Financials & driver earnings
β In-page trip notifications
β Detailed load view & analytics
β Quick βPost a Truckβ creation
β¦and many more features to grow your operations!
Upgrade today and take your workflow to the next level. πΌβ¨
β‘2π2π1π₯1
Update on Amazon Relay βQuick Reminderβ (October 7)
Data current as of Ocober 9, 2025.
What happened
On October 7, Amazon Relay sent a notification stating βQuick reminder: the portal is for direct carrier interaction and automated tools/bots arenβt allowed.β We should emphasize that this was a reminderβnot a warning. A similar reminder went out in 2023; we saw no confirmed suspensions tied to auto-refresher tools then.
What weβre seeing now
β’ Claims circulated that LoadFetcher users were suspended for using refreshers.
β’ We investigated all reports we received. Several were unsubstantiated; some suspensions pre-dated Oct 7 with no stated cause from Relay Amazon, thus it was assumed cause was LoadFetcher.
β’ As of now we have zero confirmed cases of accounts beimg suspended because of LoadFetcher.
Reminder about suspensions
Amazon can suspend accounts for many reasons, usually on sub-/double brokering cases clear reason not provided by them. If youβre impacted, ask Relay Support for the specific reason tied to your case, or contact us for assistance determining the suspension cause.
Current usage
36+ hours after the reminder, ~92% of previously active users remain active on LoadFetcher, with more returning.
Donβt panic, and donβt spread unverified claims. Get in touch with LoadFetcher support. Weβll continue to monitor and share verified updates.
Data current as of Ocober 9, 2025.
What happened
On October 7, Amazon Relay sent a notification stating βQuick reminder: the portal is for direct carrier interaction and automated tools/bots arenβt allowed.β We should emphasize that this was a reminderβnot a warning. A similar reminder went out in 2023; we saw no confirmed suspensions tied to auto-refresher tools then.
What weβre seeing now
β’ Claims circulated that LoadFetcher users were suspended for using refreshers.
β’ We investigated all reports we received. Several were unsubstantiated; some suspensions pre-dated Oct 7 with no stated cause from Relay Amazon, thus it was assumed cause was LoadFetcher.
β’ As of now we have zero confirmed cases of accounts beimg suspended because of LoadFetcher.
Reminder about suspensions
Amazon can suspend accounts for many reasons, usually on sub-/double brokering cases clear reason not provided by them. If youβre impacted, ask Relay Support for the specific reason tied to your case, or contact us for assistance determining the suspension cause.
Current usage
36+ hours after the reminder, ~92% of previously active users remain active on LoadFetcher, with more returning.
Donβt panic, and donβt spread unverified claims. Get in touch with LoadFetcher support. Weβll continue to monitor and share verified updates.
π6β€4π₯4π€©1
Media is too big
VIEW IN TELEGRAM
LoadFetcher just dropped BIG upgrades:
β¨ A new built-in map
β¨ DAT.com integration via LoadLine
β¨ More features unlocked for Free plan
β¨ Telegram alerts and Post a Truck for Plus plan
β¨ Faster, smoother real-time refresh
π Download LoadFetcher today.
https://loadfetcher.com
https://t.me/loadfetcher
β¨ A new built-in map
β¨ DAT.com integration via LoadLine
β¨ More features unlocked for Free plan
β¨ Telegram alerts and Post a Truck for Plus plan
β¨ Faster, smoother real-time refresh
π Download LoadFetcher today.
https://loadfetcher.com
https://t.me/loadfetcher
π₯5β€3π1
This media is not supported in your browser
VIEW IN TELEGRAM
Fresh update π
Team collaboration & Dark mode are hereπ€©π₯³
Make logistics smoother, faster, and stress-free π₯
π Download LoadFetcher today
https://loadfetcher.com
https://t.me/loadfetcher
Team collaboration & Dark mode are hereπ€©π₯³
Make logistics smoother, faster, and stress-free π₯
π Download LoadFetcher today
https://loadfetcher.com
https://t.me/loadfetcher
π₯3π2β€1
This media is not supported in your browser
VIEW IN TELEGRAM
Loadfetcher just leveled up π
Shared Device Pool + stronger security for growing teams.
π Download LoadFetcher today
https://loadfetcher.com
https://t.me/loadfetcher
Shared Device Pool + stronger security for growing teams.
π Download LoadFetcher today
https://loadfetcher.com
https://t.me/loadfetcher
π₯6π2β‘1π1
This media is not supported in your browser
VIEW IN TELEGRAM
New Updates are live on Loadfetcher website, extension and telegram bot!π£π£π£π£π£
π₯7π3β€2π―1
π HOS Update β Amazon Relay (March 22, 2026)
Amazon is now enforcing Hours of Service on Relay. Here's what you need to know:
β’ Amazon is rolling this out gradually β it may apply to some drivers but not others, even in the same company
β’ Based on what we're seeing, Amazon appears to be using the 70-hour / 8-day rule.
β’ Amazon calculates hours from load history.
β’ Amazon only shows driver availability on upcoming loads, in-transit loads will still show as available even if the driver is out of hours.
β’ LoadFetcher shows HOS per driver β hours used, hours left, trip breakdown, and 34-hour reset countdown
β οΈ Update LoadFetcher version to version 3.22.5 from Chrome Web Store for the most accurate HOS data. Older versions have an early version that's less accurate.
Got questions reach out to @loadfetcher_support
Amazon is now enforcing Hours of Service on Relay. Here's what you need to know:
β’ Amazon is rolling this out gradually β it may apply to some drivers but not others, even in the same company
β’ Based on what we're seeing, Amazon appears to be using the 70-hour / 8-day rule.
β’ Amazon calculates hours from load history.
β’ Amazon only shows driver availability on upcoming loads, in-transit loads will still show as available even if the driver is out of hours.
β’ LoadFetcher shows HOS per driver β hours used, hours left, trip breakdown, and 34-hour reset countdown
β οΈ Update LoadFetcher version to version 3.22.5 from Chrome Web Store for the most accurate HOS data. Older versions have an early version that's less accurate.
Got questions reach out to @loadfetcher_support
π11β€3π2π₯1
π Amazon Relay DAS HOS β What We've Learned (March 23, 2026)
We've been digging deep into how Amazon calculates Driver Assignment Support (DAS) Hours of Service, and here's what we now know so far:
The Basics:
Amazon looks at the last 8 days of a driver's activity and tracks total driving hours. Drivers who exceed 70 hours in that window get flagged as unassignable. From what we can tell, Amazon is NOT enforcing the 10-hour rest requirement.
Drivers are being rolled into DAS HOS gradually, not every driver is affected yet.
The 34-Hour Reset β But Not Really:
In theory, a flagged driver should need a full 34-hour rest before becoming assignable again. In practice? We've tracked multiple cases where depleted drivers became assignable well before 34 hours β some after 8 hours, some after 14, others after 30.
Our best guess: they may be adjusting based on demand. High-demand periods might loosen restrictions so they don't bench too many drivers at once. Or driver HOS being miscalculated.
Assigning Future Loads:
Amazon also factors in when a load starts, not just current hours. If a driver has depleted their 70 hours but a load starts 12+ hours from now, they may still be assignable because by the time that load begins, they'll have "recovered" enough hours as older trips fall outside the 8-day window.
Example: A driver with only 2 hours remaining for 34 hour rest was assigned to a load starting in 12 hours, but couldn't be assigned to one starting in 1-2 hours.
How Do I Check If a Driver Is Assignable with 100% accuracy?
The most accurate way right now is testing a driver on an upcoming load Amazon will show you if they can't be assigned.
Can I check if a driver is assignable without an upcoming load?
Not %100, but you can calculate it yourself by going through your driver's completed loads from the last 8 days and adding up the driving hours. Or you can let LoadFetcher do that math for you automatically. It pulls the driver's load history, calculates the travel time for each trip, and totals the hours against the 70-hour limit. Click on any driver in the HOS section to see the full breakdown β each load, how long it took, and how it was calculated. Team and solo trips are handled differently (team hours are split between drivers), and long solo trips use estimated travel time from origin to destination.
Make sure you're on the latest version: v3.22.10. If you're on an older version, we recommend uninstalling and reinstalling the extension to get the latest version.
We'll keep digging and share updates as we learn more.
We've been digging deep into how Amazon calculates Driver Assignment Support (DAS) Hours of Service, and here's what we now know so far:
The Basics:
Amazon looks at the last 8 days of a driver's activity and tracks total driving hours. Drivers who exceed 70 hours in that window get flagged as unassignable. From what we can tell, Amazon is NOT enforcing the 10-hour rest requirement.
Drivers are being rolled into DAS HOS gradually, not every driver is affected yet.
The 34-Hour Reset β But Not Really:
In theory, a flagged driver should need a full 34-hour rest before becoming assignable again. In practice? We've tracked multiple cases where depleted drivers became assignable well before 34 hours β some after 8 hours, some after 14, others after 30.
Our best guess: they may be adjusting based on demand. High-demand periods might loosen restrictions so they don't bench too many drivers at once. Or driver HOS being miscalculated.
Assigning Future Loads:
Amazon also factors in when a load starts, not just current hours. If a driver has depleted their 70 hours but a load starts 12+ hours from now, they may still be assignable because by the time that load begins, they'll have "recovered" enough hours as older trips fall outside the 8-day window.
Example: A driver with only 2 hours remaining for 34 hour rest was assigned to a load starting in 12 hours, but couldn't be assigned to one starting in 1-2 hours.
How Do I Check If a Driver Is Assignable with 100% accuracy?
The most accurate way right now is testing a driver on an upcoming load Amazon will show you if they can't be assigned.
Can I check if a driver is assignable without an upcoming load?
Not %100, but you can calculate it yourself by going through your driver's completed loads from the last 8 days and adding up the driving hours. Or you can let LoadFetcher do that math for you automatically. It pulls the driver's load history, calculates the travel time for each trip, and totals the hours against the 70-hour limit. Click on any driver in the HOS section to see the full breakdown β each load, how long it took, and how it was calculated. Team and solo trips are handled differently (team hours are split between drivers), and long solo trips use estimated travel time from origin to destination.
Make sure you're on the latest version: v3.22.10. If you're on an older version, we recommend uninstalling and reinstalling the extension to get the latest version.
We'll keep digging and share updates as we learn more.
π10π₯5π3β€1
This media is not supported in your browser
VIEW IN TELEGRAM
π Book better loads with LoadLine β the AI-powered dispatch tool for DAT.
Join our channel for tips, updates & early access.
Join our channel for tips, updates & early access.
π₯4π2
Media is too big
VIEW IN TELEGRAM
LoadFetcher helps Amazon Relay carriers manage everything in one place.
Load search, instant alerts, route details, and many more β all in one place.
Built to help you save time and keep trucks moving.
https://t.me/loadfetcher
Load search, instant alerts, route details, and many more β all in one place.
Built to help you save time and keep trucks moving.
https://t.me/loadfetcher
π₯4β€1π1
This media is not supported in your browser
VIEW IN TELEGRAM
π New update just dropped on Load Fetcher!
Faster. Smarter. Better than ever.
Donβt miss out β go check it now π₯
https://t.me/loadfetcher
#LoadFetcher #Update #Logistics #DispatchLife
Faster. Smarter. Better than ever.
Donβt miss out β go check it now π₯
https://t.me/loadfetcher
#LoadFetcher #Update #Logistics #DispatchLife
π₯5β€3π3
This media is not supported in your browser
VIEW IN TELEGRAM
Learn how to connect Telegram to LoadFetcher
in 3 ways via the Chrome extension,
the website, or directly from Telegram.
Get instant load notifications in your private chat or a Telegram group.
https://t.me/loadfetcher
#LoadFetcher #Update #Logistics #DispatchLife
in 3 ways via the Chrome extension,
the website, or directly from Telegram.
Get instant load notifications in your private chat or a Telegram group.
https://t.me/loadfetcher
#LoadFetcher #Update #Logistics #DispatchLife
π2π€1π«‘1
Media is too big
VIEW IN TELEGRAM
Meet the latest Loadfetcher release.
From one-click AI Chat to Multiboard, we've made load searching faster and more powerful.
https://t.me/loadfetcher
#LoadFetcher #Update #Logistics #DispatchLife
From one-click AI Chat to Multiboard, we've made load searching faster and more powerful.
https://t.me/loadfetcher
#LoadFetcher #Update #Logistics #DispatchLife
π₯6π4β€1
On restriction notification on Relay loadboard, July 16th 2026
What happened:
On July 16th 2026, some carriers started to see a notification on their Relay loadboard saying "Your access to load board has been restricted as your company being vetted for suspicious activity and compliance with the program". Many LoadFetcher users did not receive this notification. We don't know what percentage of carriers received it yet. Users reported that they're not seeing some loads.
Findings:
Several unrelated users submitted screenshots where the under the hood the description is visible: βrlb-top-banner-THEFT_CTI_VERY_LOW_WARNING-header".
The wording says THEFT. CTI could mean Cargo Theft Investigation, though this is our guess of the abbreviation.
Is it related to LoadFetcher?
We are not seeing any link of LoadFetcher to that notification. The banner code references βTHEFTβ, not software or extensions.
Amazon Relay's program policy:
As of July 18 2026, the Services section A, point 3 says: "Your company will not use robots or any other automated system to book Trips or Blocks. Your company will not manipulate geo-locations, arrival times, or departure times in any way or for any reason." This is not legal advice and we can't speak for Amazon, but the wording prohibits two things: autobooking loads and spoofing geo-locations or arrival/departure times. LoadFetcher does neither: there is no autobook, and we don't manipulate location or time of trips.
If you have any question or concern, please reach out to us via telegram: @loadfetcher_support, email at info@loadfetcher.com
What happened:
On July 16th 2026, some carriers started to see a notification on their Relay loadboard saying "Your access to load board has been restricted as your company being vetted for suspicious activity and compliance with the program". Many LoadFetcher users did not receive this notification. We don't know what percentage of carriers received it yet. Users reported that they're not seeing some loads.
Findings:
Several unrelated users submitted screenshots where the under the hood the description is visible: βrlb-top-banner-THEFT_CTI_VERY_LOW_WARNING-header".
The wording says THEFT. CTI could mean Cargo Theft Investigation, though this is our guess of the abbreviation.
Is it related to LoadFetcher?
We are not seeing any link of LoadFetcher to that notification. The banner code references βTHEFTβ, not software or extensions.
Amazon Relay's program policy:
As of July 18 2026, the Services section A, point 3 says: "Your company will not use robots or any other automated system to book Trips or Blocks. Your company will not manipulate geo-locations, arrival times, or departure times in any way or for any reason." This is not legal advice and we can't speak for Amazon, but the wording prohibits two things: autobooking loads and spoofing geo-locations or arrival/departure times. LoadFetcher does neither: there is no autobook, and we don't manipulate location or time of trips.
If you have any question or concern, please reach out to us via telegram: @loadfetcher_support, email at info@loadfetcher.com
π8