bgpreport

Network · data from 2026-11-12

AS264938 Online TELECOM

Registry name: AS264938 - Online TELECOM, BR · PeeringDB

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

Announced routes

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

2804:303c:8000::/34 No ROA Nonecovered by 2804:303c::/32 15 2%low visibility 10
2804:303c:c000::/35 No ROA Nonecovered by 2804:303c:c000::/34 1 0%low visibility 1
2804:303c:e000::/35 No ROA Nonecovered by 2804:303c:c000::/34 1 0%low visibility 1
168.232.17.0/24 No ROA Other IRR onlyRADB 672 100% 67
168.232.19.0/24 No ROA Other IRR onlyRADB 671 100% 66
168.232.18.0/24 No ROA Other IRR onlyRADB 669 99% 67
168.232.16.0/24 No ROA Other IRR onlyRADB 667 99% 67
2804:303c:c000::/34 No ROA Other IRR onlyRADB 635 100% 69

AS-SET

PeeringDB's irr_as_set for AS264938: AS264938. 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 (AS264938 isn't in the set, or no route object for AS264938 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 objectsAS264938 in itNot covered
AS264938 A single AS number, not a set: AS264938 (this network), 7 route objects.

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

  • ROA: none8
  • Route object: none3
  • Route object: RIR5
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none2804:303c:8000::/34No ROA covers it. Add a ROA for AS264938, maxLength 34.15 of 636
Route object: none2804:303c:8000::/34No route object for it. A route object for 2804:303c::/32 with origin AS264938 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264938 in the RIR database for the space.15 of 636
ROA: none2804:303c:c000::/35No ROA covers it. Add a ROA for AS264938, maxLength 35.1 of 636
Route object: none2804:303c:c000::/35No route object for it. A route object for 2804:303c:c000::/34 with origin AS264938 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264938 in the RIR database for the space.1 of 636
ROA: none2804:303c:e000::/35No ROA covers it. Add a ROA for AS264938, maxLength 35.1 of 636
Route object: none2804:303c:e000::/35No route object for it. A route object for 2804:303c:c000::/34 with origin AS264938 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264938 in the RIR database for the space.1 of 636
ROA: none168.232.17.0/24No ROA covers it. Add a ROA for AS264938, maxLength 24.672 of 673
Route object: RIR168.232.17.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none168.232.19.0/24No ROA covers it. Add a ROA for AS264938, maxLength 24.671 of 673
Route object: RIR168.232.19.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none168.232.18.0/24No ROA covers it. Add a ROA for AS264938, maxLength 24.669 of 673
Route object: RIR168.232.18.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
ROA: none168.232.16.0/24No ROA covers it. Add a ROA for AS264938, maxLength 24.667 of 673
Route object: RIR168.232.16.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
ROA: none2804:303c:c000::/34No ROA covers it. Add a ROA for AS264938, maxLength 34.635 of 636
Route object: RIR2804:303c:c000::/34Route object only in RADB. Add it in the RIR database for the space.635 of 636

Route objects not announced

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

168.232.16.0/22RADBNo ROA
2804:303c::/32RADBNo 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.