bgpreport

Network · data from 2026-11-12

AS43012 GASTABUD-SE Gastabudstaden AB

Registry name: GASTABUD-SE Gastabudstaden AB, SE · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS43012, 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.
82.96.27.0/24 Invalid: origin None 2 0%low visibility 2
93.158.86.0/24 Invalid: origin None 2 0%low visibility 2
213.80.33.0/24 Invalid: origin None 2 0%low visibility 2
77.91.216.0/21 Valid RIR databaseRIPE 673 100% 67
194.59.52.0/22 Valid RIR databaseRIPE 673 100% 67
2a02:2538::/32 Valid RIR databaseRIPE 635 100% 67

AS-SET

AS43012 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 7 are in fix.csv.

  • ROA: origin3
  • Route object: none3
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: origin82.96.27.0/24ROAs covering it name AS12552, not AS43012. If AS43012 should announce it, add a ROA for AS43012.2 of 673
Route object: none82.96.27.0/24No route object for it. Add a route object with origin AS43012 in the RIR database for the space.2 of 673
ROA: origin93.158.86.0/24ROAs covering it name AS12552, not AS43012. If AS43012 should announce it, add a ROA for AS43012.2 of 673
Route object: none93.158.86.0/24No route object for it. Add a route object with origin AS43012 in the RIR database for the space.2 of 673
ROA: origin213.80.33.0/24ROAs covering it name AS12552, not AS43012. If AS43012 should announce it, add a ROA for AS43012.2 of 673
Route object: none213.80.33.0/24No route object for it. Add a route object with origin AS43012 in the RIR database for the space.2 of 673

Route objects not announced

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

193.138.71.0/24RIPENo 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.