bgpreport

Network · data from 2026-11-12

AS265282 DOMINA NET TELECOM

Registry name: AS265282 - DOMINA NET TELECOM, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS265282, 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:2d70:80::/41 Valid Nonecovered by 2804:2d70::/32 634 100% 67
2804:2d70:100::/41 Valid Nonecovered by 2804:2d70::/32 634 100% 67
2804:2d70:300::/41 Valid Nonecovered by 2804:2d70::/32 634 100% 67
2804:2d70:380::/41 Valid Nonecovered by 2804:2d70::/32 634 100% 67
168.90.208.0/22 Valid Other IRR onlyALTDB, TC 630 94% 66
2804:2d70::/32 Valid Other IRR onlyALTDB, TC 605 95% 67
168.90.208.0/24 Valid Other IRR onlyTC 1 0%low visibility 1
168.90.209.0/24 Valid Other IRR onlyTC 1 0%low visibility 1
168.90.210.0/24 Valid Other IRR onlyTC 1 0%low visibility 1
168.90.211.0/24 Valid Other IRR onlyTC 1 0%low visibility 1

AS-SET

PeeringDB's irr_as_set for AS265282: AS265282:AS-GLOBAL. 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 (AS265282 isn't in the set, or no route object for AS265282 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 objectsAS265282 in itNot covered
AS265282:AS-GLOBAL In no IRR database read today.

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

  • Route object: none4
  • Route object: RIR6
  • AS-SET: not found1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
Route object: none2804:2d70:80::/41No route object for it. A route object for 2804:2d70::/32 with origin AS265282 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265282 in the RIR database for the space.634 of 636
Route object: none2804:2d70:100::/41No route object for it. A route object for 2804:2d70::/32 with origin AS265282 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265282 in the RIR database for the space.634 of 636
Route object: none2804:2d70:300::/41No route object for it. A route object for 2804:2d70::/32 with origin AS265282 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265282 in the RIR database for the space.634 of 636
Route object: none2804:2d70:380::/41No route object for it. A route object for 2804:2d70::/32 with origin AS265282 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265282 in the RIR database for the space.634 of 636
Route object: RIR168.90.208.0/22Route object only in ALTDB, TC. Add it in the RIR database for the space.630 of 673
Route object: RIR2804:2d70::/32Route object only in ALTDB, TC. Add it in the RIR database for the space.605 of 636
Route object: RIR168.90.208.0/24Route object only in TC. Add it in the RIR database for the space.1 of 673
Route object: RIR168.90.209.0/24Route object only in TC. Add it in the RIR database for the space.1 of 673
Route object: RIR168.90.210.0/24Route object only in TC. Add it in the RIR database for the space.1 of 673
Route object: RIR168.90.211.0/24Route object only in TC. Add it in the RIR database for the space.1 of 673
AS-SET: not foundAS265282:AS-GLOBALPeeringDB names AS265282:AS-GLOBAL; no IRR database read has it.

Route objects not announced

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

168.90.208.0/23TCValid
168.90.210.0/23TCValid

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.