bgpreport

Network · data from 2026-11-12

AS218973 ONEZEROTEL

Registry name: ONE-ZERO-GROUP-AS One Zero Group AB, SE · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS218973, 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.
145.79.144.0/24 Valid RIR databaseRADB, RIPE 671 100% 68
153.76.10.0/24 Valid RIR databaseRIPE 671 100% 68
2a13:c8c4:2282::/48 Valid RIR databaseRIPE 636 100% 69
2a07:e000:33::/48 Valid RIR databaseRIPE 635 100% 69
2a13:9500:1f1::/48 Valid RIR databaseRIPE 635 100% 69
2a13:c8c4:2280::/48 Valid RIR databaseRIPE 635 100% 69
2a13:c8c4:2281::/48 Valid RIR databaseRIPE 635 100% 69
2a13:c8c4:2283::/48 Valid RIR databaseRIPE 635 100% 69
2a13:c8c4:228c::/48 Valid RIR databaseRIPE 635 100% 69
2a13:c8c4:228d::/48 Valid RIR databaseRIPE 635 100% 69
2a13:c8c4:228e::/48 Valid RIR databaseRIPE 632 99% 69
145.79.145.0/24 Valid RIR databaseRADB, RIPE 381 57% 63

AS-SET

PeeringDB's irr_as_set for AS218973: RIPE::AS218973:AS-ALL. 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 (AS218973 isn't in the set, or no route object for AS218973 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 objectsAS218973 in itNot covered
RIPE::AS218973:AS-ALL RIPE 1113 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 1 are in fix.csv.

  • Route object: not announced1

Route objects not announced

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

2a13:c8c4:2280::/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.