bgpreport

Network · data from 2026-11-12

AS48700 Arexico

Registry name: AREXICO Julian Lang trading as Arexico, DE · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS48700, 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.

103.68.111.0/24 Invalid: origin Other origin only 2 0%low visibility 2
2a01:b40::/29 Valid Other IRR onlyRADB 635 100% 67

AS-SET

AS48700's PeeringDB record names no 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 10 are in fix.csv.

  • ROA: origin1
  • Route object: none1
  • Route object: RIR1
  • Route object: not announced7
ChangePrefix or setDetailFull-table peers
ROA: origin103.68.111.0/24ROAs covering it name AS61138, not AS48700. If AS48700 should announce it, add a ROA for AS48700.2 of 673
Route object: none103.68.111.0/24Route objects for it name AS401146. Add a route object with origin AS48700 in the RIR database for the space.2 of 673
Route object: RIR2a01:b40::/29Route object only in RADB. Add it in the RIR database for the space.635 of 636

Route objects not announced

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

2a05:b0c7:7000::/36RIPENo ROA
2a05:b0c7:7fe0::/44RIPENo ROA
2a06:1283::/32RADBValid
2a14:1ec0::/31RADBValid
2a14:1ec1::/32RADB, RIPEValid
2a14:1ec7:c000::/36RADB, RIPEValid
2a14:1ec7:c010::/44RIPEValid

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.