bgpreport

Network · data from 2026-11-12

AS44034 Hi3G Access AB

Registry name: hi3g Hi3G Access AB, SE · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS44034, 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.
2a02:aa0::/30 Valid Nonecovered by 2a02:aa0::/29 635 100% 69
2a02:aa4::/30 Valid Nonecovered by 2a02:aa0::/29 635 100% 69
37.250.0.0/16 Valid RIR databaseRIPE 673 100% 67
77.241.128.0/20 Valid RIR databaseRIPE 673 100% 67
78.156.192.0/19 Valid RIR databaseRIPE 673 100% 67
79.138.128.0/17 Valid RIR databaseRIPE 673 100% 67
80.251.192.0/20 Valid RIR databaseRIPE 673 100% 67
94.191.128.0/17 Valid RIR databaseRIPE 673 100% 67
95.209.0.0/16 Valid RIR databaseRIPE 673 100% 67
109.56.0.0/14 Valid RIR databaseRIPE 673 100% 67
212.27.0.0/19 Valid RIR databaseRIPE 673 100% 67
2.64.0.0/13 Valid RIR databaseRIPE 669 99% 67
2a02:aa0::/29 Valid RIR databaseRIPE 635 100% 69

AS-SET

PeeringDB's irr_as_set for AS44034: AS-HI3G. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS44034 isn't in the set, or no route object for AS44034 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS44034 in itNot covered
AS-HI3G RIPE 1112 Yes 0

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

  • Route object: none2
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
Route object: none2a02:aa0::/30No route object for it. A route object for 2a02:aa0::/29 with origin AS44034 covers it (filters allowing more-specifics accept it). Add a route object with origin AS44034 in the RIR database for the space.635 of 636
Route object: none2a02:aa4::/30No route object for it. A route object for 2a02:aa0::/29 with origin AS44034 covers it (filters allowing more-specifics accept it). Add a route object with origin AS44034 in the RIR database for the space.635 of 636

Route objects not announced

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

2a02:aa0::/32RIPEValid

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.