bgpreport

Network · data from 2026-11-12

AS22333 ABE - AB E-Commerce, LLC

Registry name: ABE - AB E-Commerce, LLC, US · not in PeeringDB

4IPv4 routes 0.0% RPKI valid · 0.0% with a route object
0IPv6 routes
3RPKI invalid 3 origin · 0 maxLength
1No ROA 4 with no route object for this origin
4Low visibility seen by under 10% of full-table peers
19Route objects not announced registered with origin AS22333, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS22333, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.

45.145.186.0/24 Invalid: origin None 5 1%low visibility 5
104.250.206.0/24 Invalid: origin None 1 0%low visibility 1
141.11.184.0/24 Invalid: origin Other origin only 1 0%low visibility 1
149.18.52.0/24 No ROA None 1 0%low visibility 1

AS-SET

AS22333 isn't in PeeringDB, where networks name their AS-SET.

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 27 are in fix.csv.

  • ROA: origin3
  • ROA: none1
  • Route object: none4
  • Route object: not announced19
ChangePrefix or setDetailFull-table peers
ROA: origin45.145.186.0/24ROAs covering it name AS47583, not AS22333. If AS22333 should announce it, add a ROA for AS22333.5 of 673
Route object: none45.145.186.0/24No route object for it. Add a route object with origin AS22333 in the RIR database for the space.5 of 673
ROA: origin104.250.206.0/24ROAs covering it name AS50304, AS200525, not AS22333. If AS22333 should announce it, add a ROA for AS22333.1 of 673
Route object: none104.250.206.0/24No route object for it. Add a route object with origin AS22333 in the RIR database for the space.1 of 673
ROA: origin141.11.184.0/24ROAs covering it name AS834, not AS22333. If AS22333 should announce it, add a ROA for AS22333.1 of 673
Route object: none141.11.184.0/24Route objects for it name AS834. Add a route object with origin AS22333 in the RIR database for the space.1 of 673
ROA: none149.18.52.0/24No ROA covers it. Add a ROA for AS22333, maxLength 24.1 of 673
Route object: none149.18.52.0/24No route object for it. Add a route object with origin AS22333 in the RIR database for the space.1 of 673

Route objects not announced

Route objects with origin AS22333 whose prefix no peer sees AS22333 announce. Many are kept on purpose (backup routes, space announced only in some places).

45.43.7.0/24ARIN, RADBValid
45.43.8.0/24ARIN, RADBValid
66.11.125.0/24ARIN, RADBValid
104.192.103.0/24ARIN, RADBValid
139.190.44.0/24RADBNo ROA
139.190.45.0/24RADBNo ROA
139.190.46.0/24RADBNo ROA
139.190.47.0/24RADBNo ROA
139.190.52.0/24RADBNo ROA
139.190.53.0/24RADBNo ROA
139.190.54.0/24RADBNo ROA
139.190.55.0/24RADBNo ROA
139.190.56.0/24RADBNo ROA
139.190.57.0/24RADBNo ROA
139.190.58.0/24RADBNo ROA
139.190.59.0/24RADBNo ROA
154.6.70.0/23RADBNo ROA
154.6.138.0/23RADBNo ROA
193.148.12.0/24RADBNo ROA

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.