bgpreport

Network · data from 2026-11-12

AS269075 marques e santos internet

Registry name: AS269075 - GO-NET FIBRA, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS269075, 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:5f14::/41 Valid Nonecovered by 2804:5f14::/33 347 55% 65
2804:5f14::/34 Valid Nonecovered by 2804:5f14::/33 1 0%low visibility 1
2804:5f14:4000::/34 Valid Nonecovered by 2804:5f14::/33 1 0%low visibility 1
2804:5f14:8000::/34 Valid Nonecovered by 2804:5f14:8000::/33 1 0%low visibility 1
2804:5f14:c000::/34 Valid Nonecovered by 2804:5f14:8000::/33 1 0%low visibility 1
45.179.108.0/22 Valid Other IRR onlyRADB, TC 672 100% 67
2804:5f14::/32 Valid Other IRR onlyRADB, TC 635 100% 70
2804:5f14::/33 Valid Other IRR onlyTC 347 55% 65
2804:5f14:8000::/33 Valid Other IRR onlyTC 347 55% 65
45.179.108.0/23 Valid Other IRR onlyRADB, TC 185 27% 53
45.179.110.0/23 Valid Other IRR onlyRADB, TC 185 27% 53
45.179.108.0/24 Valid Other IRR onlyRADB, TC 4 1%low visibility 4
45.179.109.0/24 Valid Other IRR onlyRADB, TC 2 0%low visibility 2
45.179.110.0/24 Valid Other IRR onlyRADB, TC 2 0%low visibility 2
45.179.111.0/24 Valid Other IRR onlyRADB, TC 2 0%low visibility 2

AS-SET

PeeringDB's irr_as_set for AS269075: AS269075:AS-ANNOUNCEMENTS. 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 (AS269075 isn't in the set, or no route object for AS269075 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 objectsAS269075 in itNot covered
AS269075:AS-ANNOUNCEMENTS TC 4241 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 15 are in fix.csv.

  • Route object: none5
  • Route object: RIR10
ChangePrefix or setDetailFull-table peers
Route object: none2804:5f14::/41No route object for it. A route object for 2804:5f14::/33 with origin AS269075 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269075 in the RIR database for the space.347 of 636
Route object: none2804:5f14::/34No route object for it. A route object for 2804:5f14::/33 with origin AS269075 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269075 in the RIR database for the space.1 of 636
Route object: none2804:5f14:4000::/34No route object for it. A route object for 2804:5f14::/33 with origin AS269075 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269075 in the RIR database for the space.1 of 636
Route object: none2804:5f14:8000::/34No route object for it. A route object for 2804:5f14:8000::/33 with origin AS269075 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269075 in the RIR database for the space.1 of 636
Route object: none2804:5f14:c000::/34No route object for it. A route object for 2804:5f14:8000::/33 with origin AS269075 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269075 in the RIR database for the space.1 of 636
Route object: RIR45.179.108.0/22Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR2804:5f14::/32Route object only in RADB, TC. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:5f14::/33Route object only in TC. Add it in the RIR database for the space.347 of 636
Route object: RIR2804:5f14:8000::/33Route object only in TC. Add it in the RIR database for the space.347 of 636
Route object: RIR45.179.108.0/23Route object only in RADB, TC. Add it in the RIR database for the space.185 of 673
Route object: RIR45.179.110.0/23Route object only in RADB, TC. Add it in the RIR database for the space.185 of 673
Route object: RIR45.179.108.0/24Route object only in RADB, TC. Add it in the RIR database for the space.4 of 673
Route object: RIR45.179.109.0/24Route object only in RADB, TC. Add it in the RIR database for the space.2 of 673
Route object: RIR45.179.110.0/24Route object only in RADB, TC. Add it in the RIR database for the space.2 of 673
Route object: RIR45.179.111.0/24Route object only in RADB, TC. Add it in the RIR database for the space.2 of 673

Route objects not announced

Every route object with origin AS269075 is announced.

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.